linkfox-wb-mpstats-ozon

[!IMPORTANT] This Skill must rely on the MCP "LinkFox". If this MCP is not installed, please clearly notify the user: Please install the LinkFox connector first:

In the left side of WorkBuddy, find "Experts · Skills · Connectors" → "Connectors";

Search for the keyword "LinkFox" and install the connector "LinkFox" (note: it is linkfox, not linkfox-product-selection), and complete login authorization by following the instructions;

Return to WorkBuddy and retry.

LinkFox MPSTATS Ozon Product Selection (LinkFox MPSTATS Ozon Product Intelligence)

This capability is used to turn Ozon Russia marketplace product data into verifiable product selection and competitor research results: first find products by Russian keywords or SKU, then view price, sales volume, sales revenue, rating, inventory, turnover, ranking, and time trends by SKU, brand, category, or seller. It covers 6 business sub-capabilities and, through WorkBuddy's LinkFox.proxy_call invokes 6 precise endpoint toolNames. Sub-capability identifiers, parameters, and toolNames are listed item by item in the routing table below and in the corresponding references.

Capability boundaries

Capability scope

Product discovery and identity resolution（linkfox-mpstats-ozon-product-search): Search products using Russian keywords or an Ozon SKU list, returning identity fields such as productId, Russian title, product page, main image, brand, and seller, which are suitable as an entry point for subsequent detail, trend, or dimension analysis.
SKU product card verification（linkfox-mpstats-ozon-product-detail): Batch-query product details for existing SKUs, up to 100 per request, returning fields such as price, discount, Ozon Card price, rating, review count, inventory, delivery options, sales volume/sales revenue for the statistical period, comparison with the previous period, potential sales revenue, and out-of-stock losses; the server processes SKUs concurrently and automatically retries failed items once, allowing partial success.
Single-SKU daily trend（linkfox-mpstats-ozon-product-trend): Around a productId , view daily price, sales volume, inventory, rating, review count, and bestseller/new product flags for a specified date window;includeSearchStats search visibility expansion can be requested, but the actual returned schema shall prevail.
Brand-dimension product insights（linkfox-mpstats-ozon-brand-products): Query SKUs of a brand by the brand name displayed on the Ozon storefront, supporting numeric filters, sorting, pagination, currency conversion, and FBO/FBS mode switching, for observing brand product structure, hit products, and sales revenue share.
Category-dimension product insights（linkfox-mpstats-ozon-category-products): Query products by the full Russian category path used by Ozon, supporting multi-condition filtering by sales volume, price, rating, inventory, turnover, lost sales revenue, etc., as well as within-category ranking, for scanning category hit products and niche opportunities.
Seller-dimension product insights（linkfox-mpstats-ozon-seller-products): Query store SKUs by numeric sellerId , supporting the same filtering, sorting, pagination, currency, and FBO/FBS options as the brand/category dimensions, for store structure, seller hit products, and competitor store benchmarking.
Unified research workflow: The productId、brand、brandId、sellerId and category in the discovery results can continue to be used for SKU details, trends, or brand/category/seller drill-down; the costToken、costTime and date fields in each query result are used to audit call costs and data time points.

Boundaries and limitations

Site scope: Covers only MPSTATS Ozon Russia marketplace data, not Wildberries or other Russian/global e-commerce platforms.
Data time point: The statistical interface's endDate is at the latest yesterday (T-1); today's or a future date cannot be passed; a missing date is handled by the interface according to the rules of each operation.
Input must match the dimension: For search, provide at least keyword or productIds; for details, a SKU list must be provided; for trends, only one numeric productIdcan be provided at a time; the brand must be the exact Ozon display name; the category must be the full Russian path; the seller must be a numeric string sellerId。
Search is not a metrics interface：productSearch is an identity resolution interface that always returns about 10 identity fields and does not return price, sales, ratings, inventory, turnover, or ranking; when these metrics are needed, you must switch to details or drill down under the corresponding dimension.
Capacity limits: Product details support at most 100 SKUs per request; brands, categories, and sellers support at most 100 rows per page; product search has no pagination, sorting, or filtering parameters, and a single result has a hard upstream limit of about 36 items; trends support only one SKU per request.
Caliber limits: For brand/category/seller results, revenueSharePercent is the share within the result set of the current query dimension, not the site-wide share;position also corresponds to the current query dimension.includeFbs is a caliber switch shared by the entire batch or the entire query and cannot be set per individual SKU.
Language and names: Keywords, category paths, and brand names should preferentially use the Russian or Latin forms actually used by Ozon. English/Chinese keywords should first be converted to Russian and the conversion indicated; brands do not support fuzzy matching, and spelling errors may return empty results.
Time series gaps: For trend points, hasData=false indicates no observation, which is not equal to zero sales; likewise, do not treat missing fields as zero. The current schema of the trend interface does not guarantee an additional independent search ranking field.
Data usage: The results are market data and query results, not procurement commitments, sales guarantees, or financial/business conclusions; they do not include review text, Listing copy optimization, advertising placement, orders, logistics, supply chain, or profit calculation recommendations.

Tool selection guide

Need / User says	Default recommendation	When to switch to another
"Search for a product/keyword on Ozon" "I have a batch of Ozon SKUs; first tell me the product names"	`linkfox-mpstats-ozon-product-search`; a Russian keyword or `productIds` provide at least one	When you already have SKUs and want price, sales, inventory, and ratings, switch to `linkfox-mpstats-ozon-product-detail`; when you already have a brand, category, or seller dimension, directly use the corresponding drill-down
"Check the price, sales, ratings, and inventory of these SKUs" "View competitor product cards in bulk"	`linkfox-mpstats-ozon-product-detail`; suitable for statistical-period summaries of 1–100 SKUs	To see daily changes for only one SKU, switch to `linkfox-mpstats-ozon-product-trend`; to get the product set under a certain brand/category/store, switch to the corresponding `*-products`
"How have this Ozon SKU's sales/price changed recently" "Check whether there is seasonality or stockout"	`linkfox-mpstats-ozon-product-trend`; one SKU, one date window	If you only want a product card for the current statistical period, switch to `product-detail`; do not loop the trend interface as a substitute for multiple SKUs or dimension filtering
"See what adidas/Xiaomi sells on Ozon" "Brand bestsellers/brand sales structure"	`linkfox-mpstats-ozon-brand-products`；`brandName` must be a display name	If you do not know the exact brand spelling, first use `product-search`; to compare across brands and categories, switch to `category-products`; to switch to store products, use `seller-products`
"find a hit/blue-ocean SKU in a certain Ozon category" "filter sales, price, turnover"	`linkfox-mpstats-ozon-category-products`; need full Russian `categoryPath` and optional `filters`	If you don't know the full path, start from the detail result's `category` or search results to locate it; when looking at only one brand/store, switch to `brand-products`/`seller-products`
"break down a certain Ozon seller's store" "view competitor store SKUs, sales, and out-of-stock losses"	`linkfox-mpstats-ozon-seller-products`; need numeric `sellerId`	If you only have the seller name, first use `product-search` to resolve `sellerId`; to get a category or brand set, switch to the corresponding drill-down

When choosing, first determine the user's primary dimension: if there is no ID, do discovery; if there is already a SKU and summary metrics are asked, do detail; only do trend when asking "how does it change over time"; if a brand name, full category path, or seller ID already exists, directly use the corresponding drill-down. When multiple candidates can satisfy the request, prioritize the operation that can directly answer the question and has the fewest requests, and confirm FBO/FBS, date window, pagination, and currency as unified parameters. Each real request may consume credits, so inform the user before expanding SKUs, pagination, or changing parameters.

Business requirement routing quick reference

Sub-capability	Business capability	reference	`toolName`	Local helper
`linkfox-mpstats-ozon-product-search`	Russian keyword / SKU product search and identity resolution	`references/linkfox-mpstats-ozon-product-search.md`	`mpstats/ozon/productSearch`	None
`linkfox-mpstats-ozon-product-detail`	1–100 SKU product cards and statistical period summary	`references/linkfox-mpstats-ozon-product-detail.md`	`mpstats/ozon/productDetail`	None
`linkfox-mpstats-ozon-product-trend`	Single SKU daily price, sales, inventory, and performance trend	`references/linkfox-mpstats-ozon-product-trend.md`	`mpstats/ozon/productTrend`	None
`linkfox-mpstats-ozon-brand-products`	SKU filtering, sorting, pagination, and metric analysis under a brand	`references/linkfox-mpstats-ozon-brand-products.md`	`mpstats/ozon/brandProducts`	None
`linkfox-mpstats-ozon-category-products`	SKU filtering and ranking analysis under a Russian category path	`references/linkfox-mpstats-ozon-category-products.md`	`mpstats/ozon/categoryProducts`	None
`linkfox-mpstats-ozon-seller-products`	SKU filtering, sorting, and structural analysis for a seller store	`references/linkfox-mpstats-ozon-seller-products.md`	`mpstats/ozon/sellerProducts`	None

MCP invocation method

MCP Server：LinkFox; the unified tool is proxy_call。
Parameter structure：proxy_call of toolName must use the exact value from the routing table, case-sensitive and without a leading /; put business parameters directly in arguments, do not wrap another layer of body、params or data。
Authorization: WorkBuddy automatically injects the authorization context. It is forbidden to pass arguments in headers、Authorization, API Key, token, JWT, or phone number, and do not read local environment variables to supplement authentication.
Response handling：proxy_call If the result is a JSON string, parse it only once; after parsing, handle it according to the reference's response field table. First distinguish MCP transport/configuration errors, then handle downstream business code/errcode and msg/errmsg。
Failure discipline: do not fall back to the old HTTP gateway, old Python scripts, or other undeclared tools. On failure, empty results, or partial success, do not automatically switch keywords, turn pages, change brand spelling, or continuously change dates to probe, and do not repeatedly initiate billed calls to "confirm results". If a retry is truly needed, or you need to expand page/list or switch includeFbs , first explain to the user the possible extra credit consumption and obtain consent.
Full parameter location: each operation's required conditions, all optional parameters, full response fields, error codes, and Feedback API are in references/<子能力标识>.md; unified guidance for authentication or billing exceptions is in references/onboarding.md。
Migrated local capabilities: This skill does not keep local helpers. The 24-hour parameter cache, automatic JSON persistence, session index, and stdout summary provided by the old script are not part of the MCP return capability; when retention or summarization is needed, it should be explicitly handled by the current WorkBuddy session, and it must not be claimed that MCP has completed it automatically.

Usage examples

All parameters below come from the corresponding operation. Dates in the examples cannot be later than yesterday; Russian titles and brands are kept in the original by default, and can be translated as needed when displayed.

1. Keyword discovery and SKU reverse lookup

{"keyword":"кроссовки","startDate":"2025-03-01","endDate":"2025-03-31"}

Call toolName="mpstats/ozon/productSearch" with proxy_call. In the output, focus on products[].productId/title/brand/sellerId/sellerName/productPageUrl/imageUrl、total and costToken。keyword and productIds at least one must be present; search has no pagination and is capped at about 36 items per call, so do not treat it as a sales volume interface.

{"productIds":[1786874757,151623766,142257239]}

This is batch SKU identity resolution for the same operation. If business metrics are needed next, pass the returned productId to product details instead of inferring price or sales from search results.

2. SKU product cards and period comparison

{
  "productIds":[1786874757,151623766,142257239],
  "startDate":"2025-03-01",
  "endDate":"2025-03-31",
  "includeFbs":true
}

Call toolName="mpstats/ozon/productDetail" with proxy_call. In the output, look at products[] of price/monthlySalesUnits/monthlySalesRevenue/rating/reviewCount/balance/deliveryScheme; when out-of-stock impact is needed, also look at revenuePotential/lostProfit/lostProfitPercent, and place previousSalesUnits/previousRevenue alongside the current period value. Batches over 100 must be split; whenfailedCount > 0 , list the SKUs in failures and do not silently drop them.

3. Single-SKU daily trend

{
  "productId":1786874757,
  "startDate":"2025-03-01",
  "endDate":"2025-03-31",
  "includeFbs":true,
  "includeSearchStats":true
}

Call toolName="mpstats/ozon/productTrend" with proxy_call. The output is the top-level data[]; read it day by day. date/hasData/price/sales/balance/rating/comments/isBestseller/isNew；hasData=false is a missing observation and should not be rewritten as zero sales. When the current schema does not declare additional search fields, explicitly state that search position is unavailable. Daily sales are not in the output; if the user requests them, only use sales * price for estimation and mark it as an estimate.

4. Brand product filtering

{
  "brandName":"adidas",
  "filters":[
    {"field":"rating","op":"GTE","value":4.5},
    {"field":"final_price","op":"BETWEEN","value":1000,"value2":5000}
  ],
  "sortField":"revenue",
  "sortDirection":"desc",
  "pageSize":50,
  "currency":"USD",
  "includeFbs":true
}

Call toolName="mpstats/ozon/brandProducts" with proxy_call. Filter conditions are treated as AND;BETWEEN must be provided with value2; in the output, look at the 39-field product cards in products[] and the brand dimension position/revenueSharePercent. After conversion, mark USD in the table header; exact brand names do not support fuzzy matching.

5. Category opportunity scan

{
  "categoryPath":"Одежда/Женская одежда/Футболки и топы женские",
  "filters":[
    {"field":"sales","op":"GTE","value":50},
    {"field":"turnover_days","op":"LTE","value":30}
  ],
  "sortField":"revenue",
  "sortDirection":"desc",
  "page":1,
  "pageSize":100
}

Call toolName="mpstats/ozon/categoryProducts" with proxy_call。categoryPath must be the full Ozon Russian path; total in the results is used to determine whether there is a next page, and the category-dimension position/revenueSharePercent should not be interpreted as a site-wide ranking/share. For unknown paths, first obtain category from product details or search results.

6. Seller shop breakdown

{
  "sellerId":"3628678",
  "sortField":"lost_profit",
  "sortDirection":"desc",
  "filters":[{"field":"sales","op":"GTE","value":30}],
  "pageSize":100,
  "currency":"RUB"
}

Call toolName="mpstats/ozon/sellerProducts" with proxy_call。sellerId must be a numeric string; in the output, focus on productId/title/brand/monthlySalesUnits/monthlySalesRevenue/balance/turnoverDays/lostProfit/position. If only the seller name is available, first resolve the numeric sellerId, and do not pass the name directly to the seller endpoint.

Display rules

Present columns according to the query purpose: for search results, first show productId, Russian title、brand、sellerName、sellerId, and use the product page and main image as auxiliary columns; do not fill in price, sales, rating, or stock for search results.
Use a compact table for product cards: for details, prioritize showing productId、title、price、monthlySalesUnits、monthlySalesRevenue、rating、reviewCount、balance、deliveryScheme、firstDate; only expand potential sales and lost sales when the user asks about out-of-stock impact.
Preserve the time basis: previous* in the details is the equal-length previous period; call it a period-over-period change only when both the current value and the previous-period value are given; display trends row by row by date or in a sparkline-friendly format, and do not replace the daily shape with aggregate numbers.
Correctly explain missing and anomalous data: trend hasData=false and sales=0, hasData=true are marked separately; when search statistics have no actual fields, state that they are unavailable; in the response, failures, empty lists, and missing fields must be displayed truthfully and must not be silently discarded or replaced with estimates posing as original values.
Indicate currency and dimension: the default Ozon amount basis is RUB; when displaying price/sales, note currency; for brand, category, and seller results, revenueSharePercent is labeled "share within the current query dimension result set", andposition is labeled with the specific dimension. When using USD/EUR/CNY, state that conversion was performed according to the requested currency and whether a custom currencyRate。
Indicate delivery and inventory basis: display deliveryScheme or isFbs; mixed FBO/FBS results should be flagged with their basis, andincludeFbs applies to the entire request.salesPerDayWithStock/dailySalesRevenueWithStock represents in-stock days only; do not mix it with the daily average over the full window.
Pagination and limits transparent: brand, category, and seller results report total, the current page, and pageSize; when search reaches the upstream limit, suggest narrowing keywords, SKUs, or dates rather than fabricating a next page; for failed detail items, list the SKU and error message.
Preserve the original text and translate on request: by default, retain Russian product titles, brands, category paths, and seller names; when providing translations to Chinese/English users, retain the original text at the same time to avoid changing values used for re-querying.
Source, time, and cost auditable: when displaying or exporting, retain sourceType/sourceTool(if provided by the response), the query date window,costTime , and costToken; rely on the actual response of this MCP session, and do not claim that it has been automatically persisted to disk or cached by a script.
Present objectively: only describe the market data, filter conditions, and observable phenomena returned by MPSTATS; do not directly elevate rankings, sales, or lost sales into business conclusions such as "guaranteed hit" or "definitely worth sourcing".
Provide correction suggestions for errors: explain code/errcode and msg/errmsg as-is; for missing required parameters, Russian keywords, complete category paths, exact brand names, numeric seller IDs, dates beyond yesterday, and page size/detail batch overruns, provide the corresponding input correction directions.

Resolve authentication and credit issues

When the following exceptions occur, read references/onboarding.md. WorkBuddy automatically handles call authorization; do not request, display, or guess API Keys, tokens, JWTs, phone numbers, or payment status.

Exceptions

MCP tool does not exist or is unavailable: this is a WorkBuddy/MCP configuration or loading issue; prompt to check whether LinkFox is configured and refresh the session; do not switch to the legacy HTTP gateway.
401 / authorized error: this is a WorkBuddy automatic authorization context exception; prompt to refresh the session or check the connection, and do not pass any credentials in the parameters.
402 / insufficient credits or balance: when the response is HTTP 402,errcode=402, or the message contains meanings such as "insufficient credits/insufficient billing/insufficient balance/quota exceeded/insufficient balance/plan expired/recharge required/please recharge", read the plan and let the user decide whether to purchase; do not place an order automatically.
Other business errors: 403 means no permission and is not classified as auth/billing; correct input errors, empty results, and date/batch limits according to the error codes in each reference, and do not use onboarding in place of business troubleshooting.

When points are insufficient, guide the user to visit https://agent.linkfox.com/ for self-service handling; do not automatically read plans, place orders, make payments, or poll orders.

Points consumption notice

Users will be charged for points consumption. Evaluate thoroughly: when this skill needs to be called frequently, or when the user has insufficient expectations about the amount of points consumed, be sure to remind the user and let the user decide whether to continue.