linkfox-wb-seerfar-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 WorkBuddy, find "Experts · Skills · Connectors" on the left → "Connectors";

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

Return to WorkBuddy and retry.

LinkFox Ozon Product Research

Aimed at Ozon product selection, keyword research, and competitor breakdown, outputting verifiable market metrics, product lists, store/category summaries, and single-product trend data. Capabilities cover 7 sub-capabilities, 7 APIs/operations, associated tool_key=seerfar_ozon：linkfox-seerfar-ozon-market-keyword-search、linkfox-seerfar-ozon-keyword-mining、linkfox-seerfar-ozon-keyword-back-search、linkfox-seerfar-ozon-shop-search、linkfox-seerfar-ozon-category-search、linkfox-seerfar-ozon-product-detail-search、linkfox-seerfar-ozon-product-report-search。

MCP invocation

item	fixed value
MCP server	`LinkFox`
unique tool	`proxy_call`
`toolName` allowlist	`seerfar/ozon/marketKeywordSearch`、`seerfar/ozon/keywordMining`、`seerfar/ozon/keywordBackSearch`、`seerfar/ozon/shopSearch`、`seerfar/ozon/categorySearch`、`seerfar/ozon/productDetailSearch`、`seerfar/ozon/productReportSearch`
call structure	`{"toolName":"<精确 endpoint>","arguments":{...}}`; the original request body is directly used as `arguments`

toolName must be selected from the allowlist, with exact matching and case sensitivity.
WorkBuddy automatically injects MCP Authorization; MCP configuration, documentation, and arguments must not add headers, API Key, token, JWT, phone number, or other credentials.
curl,urllib、requests、httpx or other HTTP methods are prohibited from directly connecting to the tool gateway; stop when MCP or proxy_call is missing, and do not silently fall back.
Within the same task, the same toolName + arguments must not be called repeatedly; when a paid call fails, returns empty results, or the results are unsatisfactory, do not automatically retry or probe with changed conditions.
First check the MCP connection, schema, and isError, then read text/structured content; when text is a JSON string, parse it only once. Then check the downstream errcode、errorCode、code、errmsg or msg, and finally read the business fields.
The new MCP link does not provide the old script's 24-hour cache, JSON persistence to disk, or stdout summary; only non-sensitive call summaries and statuses are retained for result traceability.

Capability boundaries

Capability scope

Market hot words and market profile: Filter market keywords by search popularity, 30-day growth, product/competitor/seller count, price, sales, market space, and conversion concentration; use linkfox-seerfar-ozon-market-keyword-search and seerfar/ozon/marketKeywordSearch。
Seed word expansion and long-tail mining: Discover related words around a Russian or other user-provided seed word, and filter by relevance, title density, search volume, competition, and add-to-cart conversion; use linkfox-seerfar-ozon-keyword-mining and seerfar/ozon/keywordMining。
SKU keyword reverse lookup: Reverse lookup natural search terms and ad search terms from up to 20 product SKUs, including each term's natural rank, ad rank, impressions, and conversion; use linkfox-seerfar-ozon-keyword-back-search and seerfar/ozon/keywordBackSearch。
Store products and seller structure: View product sales, price, rating, delivery method, seller type, and store summary by paging through seller/store IDs; use linkfox-seerfar-ozon-shop-search and seerfar/ozon/shopSearch。
Category capacity and product rankings: Obtain category total sales, total revenue, average price, rating, seasonality, and product list by category ID, viewable by historical month and delivery method; use linkfox-seerfar-ozon-category-search and seerfar/ozon/categorySearch。
Single-product in-depth evaluation: View price, rating, sales, revenue, inventory, category ranking, daily sales trend, brand, seller, fulfillment method, and listing duration by individual SKU; use linkfox-seerfar-ozon-product-detail-search and seerfar/ozon/productDetailSearch。
Product report filtering: Filter products by sales, revenue and growth, conversion, price, rating, reviews, gross margin, return/cancellation rate, brand, seller, fulfillment method, listing time, and tags; use linkfox-seerfar-ozon-product-report-search and seerfar/ozon/productReportSearch。
Result traceability: The new MCP pipeline does not guarantee the summaries, caching, or disk persistence of the old scripts; display only necessary fields on demand, and record non-sensitive call summaries and statuses.

Boundaries and limitations

All queries are automatically authorized by WorkBuddy and consume credits per API call; within the same task, identical toolName + arguments is called only once. On failure or empty results, do not automatically swap terms, change filter conditions, paginate, or retry as probing; before continuing to call, first remind the user and let the user decide.
Data is primarily Ozon; keyword-type results may include platform=1 Wildberries rows, the API has no platform input selector, and distinction must be made client-side based on the returned platform . Product, store, and category queries should not be inferred from this to be data from other platforms.
page is a required object for list queries; for store and category pageSize the maximum is 20; market keyword, keyword mining, and reverse lookup lists should also use pagination and sorting. Category IDs, store IDs, and SKUs must use identifiers recognizable by Seerfar and must not be replaced with human-readable names.
Keyword market search must pass page; keyword mining must pass keyword and page; keyword reverse lookup must pass skuIds、hasVariant and page; store must pass id and page; category must pass categoryId and page; single product detail must pass sku; product report must pass page。
Keyword market search is used for full-market keyword browsing, with optional searchDate and categories; keyword mining is used to expand around seed terms, and does not support searchDate、categories; keyword reverse lookup is used for SKU→keyword, does not accept seed keyword, and historical time uses historyDate。
Store/category lists are paginated views; whentotal does not equal the full store/category scale, use hasNextPage to continue judging; product detail is a single-SKU query and cannot be batched; for product reports, skus is at most 10.
Sales, revenue, inventory, conversion, gross margin, ranking, and trends are Seerfar data or model estimates and are not equivalent to Ozon official backend data; some fields may not be returned due to product type, platform seller, or missing upstream data.
Does not provide Ozon account operations, listing, orders, inventory writing, ad delivery, logistics fulfillment, supply chain execution, or other platform operation actions; does not guarantee product selection success, nor does it make unsupported profit or competition conclusions for the user.

Tool selection guide

Need / user says	Default recommendation	When to switch to another
"What are Ozon's hot keywords" "Find blue-ocean keywords by search volume/seller count"	`linkfox-seerfar-ozon-market-keyword-search`	If you already have seed terms and want related terms, switch to keyword mining; if you already have a SKU and want traffic keywords, switch to keyword reverse lookup
"Find long-tail/related terms around this Russian word"	`linkfox-seerfar-ozon-keyword-mining`	No seed is provided; to view whole-market terms, switch to market hot words; to reverse-look up ranked terms for a product, switch to keyword reverse lookup
"Under which organic terms/ad terms does this SKU rank"	`linkfox-seerfar-ozon-keyword-back-search`	To get product sales/inventory/trends, switch to single product details; to filter products by multiple metrics, switch to product reports
"What does this store sell, what are its hit products, and what are the store's total sales"	`linkfox-seerfar-ozon-shop-search`	When only the store name or product name is available, first obtain it through product/list results `sellerId`; to get category size, switch to category query
"How big is this Ozon category, and what are the category's best-selling products/price bands"	`linkfox-seerfar-ozon-category-search`	When only the category name is available, first resolve `categoryId`; to use the store dimension, switch to store query
"View the details, inventory, ranking, or sales trend of a SKU"	`linkfox-seerfar-ozon-product-detail-search`	To filter multiple products at once or rank by metrics, switch to product reports; to get the product's keywords, switch to keyword reverse lookup
"Filter Ozon products by sales, price, rating, gross margin/find hit products"	`linkfox-seerfar-ozon-product-report-search`	To get daily trends for a single SKU, switch to single product details; for category-level summaries, switch to category query; for a store's full catalog, switch to store query

When choosing, first determine whether the entity the user wants to query isa keyword, SKU, store, or category, then determine whether it is discovery/filtering, reverse lookup, or in-depth details; at the same time check required IDs, time windows, sort fields, and list limits. When multiple choices can satisfy the need, explain each one's input/output parameters, data granularity, and additional call cost, and let the user decide whether to continue.

Business requirement routing quick reference

Sub-capability	Business capability	reference / API reference	`toolName`	Local assistance
`linkfox-seerfar-ozon-market-keyword-search`	Whole-market hot word filtering and keyword market profiling	`references/linkfox-seerfar-ozon-market-keyword-search.md` / `references/linkfox-seerfar-ozon-market-keyword-search-api.md`	`seerfar/ozon/marketKeywordSearch`	None
`linkfox-seerfar-ozon-keyword-mining`	Mine related terms and long-tail terms around seed words	`references/linkfox-seerfar-ozon-keyword-mining.md` / `references/linkfox-seerfar-ozon-keyword-mining-api.md`	`seerfar/ozon/keywordMining`	None
`linkfox-seerfar-ozon-keyword-back-search`	Reverse-look up organic terms, ad terms, and ranking metrics by SKU	`references/linkfox-seerfar-ozon-keyword-back-search.md` / `references/linkfox-seerfar-ozon-keyword-back-search-api.md`	`seerfar/ozon/keywordBackSearch`	None
`linkfox-seerfar-ozon-shop-search`	Store product catalog, seller type, and store summary	`references/linkfox-seerfar-ozon-shop-search.md` / `references/linkfox-seerfar-ozon-shop-search-api.md`	`seerfar/ozon/shopSearch`	None
`linkfox-seerfar-ozon-category-search`	Category capacity, seasonality, and category product rankings	`references/linkfox-seerfar-ozon-category-search.md` / `references/linkfox-seerfar-ozon-category-search-api.md`	`seerfar/ozon/categorySearch`	None
`linkfox-seerfar-ozon-product-detail-search`	Single SKU details, sales trends, inventory, and ranking	`references/linkfox-seerfar-ozon-product-detail-search.md` / `references/linkfox-seerfar-ozon-product-detail-search-api.md`	`seerfar/ozon/productDetailSearch`	None
`linkfox-seerfar-ozon-product-report-search`	Multi-metric product report filtering and product-level ranking	`references/linkfox-seerfar-ozon-product-report-search.md` / `references/linkfox-seerfar-ozon-product-report-search-api.md`	`seerfar/ozon/productReportSearch`	None

Each reference file contains the corresponding capability description, boundaries, parameters, and usage rules; the same-named -api.md file retains the complete request parameters, response fields, error codes, MCP, and response examples.

Call method

Select a reference and the corresponding exact toolName。
according to [Business requirement routing quick reference]; construct argumentsfrom the reference request parameter table, and pass the original request object directly without adding transport-layer fields.
Use proxy_call to call once; do not repeatedly make charged calls with the same parameters, and do not guess other toolName。
after a failure; parse in the order of MCP outer layer, proxy content, downstream business error, and business fields. For the complete schema, error codes, response examples, and the standalone Feedback API, see the same-named -api.md。

Usage examples

The following examples are all real arguments shapes. Before execution, confirm the required IDs and credit budget; each response may contain costToken。

1. Whole-market hot words and blue-ocean filtering

{
  "page": {"page": 1, "pageSize": 20, "orders": [{"field": "searchVolume", "direction": "DESC"}]},
  "searchVolume": {"min": 10000},
  "sellers": {"max": 50}
}

Use toolName=seerfar/ozon/marketKeywordSearch to call proxy_call. Focus on reading data[].query/queryCn、searchVolume、count30GrowthRate、productCount、sellers、avgPrice、marketSpace and products[]；platform=0/1 are labeled Ozon/Wildberries respectively. The interface must have page, and cannot use a human-readable category name in place of categories。

2. Mine long-tail keywords around seed words

{
  "keyword": "телефон",
  "page": {"page": 1, "pageSize": 20, "orders": [{"field": "relevancy", "direction": "DESC"}]},
  "matchType": 1,
  "includeKeywords": ["женские"],
  "excludeKeywords": ["ремень"],
  "searchVolume": {"min": 1000},
  "sellers": {"max": 50}
}

Use toolName=seerfar/ozon/keywordMining to call proxy_call. Read query/queryCn、relevancy、titleDensity、wordCount and market metrics; the interface must have keyword and page, does not support searchDate、categories, and cannot be used as a whole-market hot-keyword browsing interface.

3. Reverse-lookup a SKU's organic or ad keywords

{
  "skuIds": [4380710124],
  "hasVariant": 1,
  "type": ["0"],
  "naturalRank": {"max": 10},
  "page": {"page": 1, "pageSize": 20, "orders": [{"field": "searchVolume", "direction": "DESC"}]}
}

Use toolName=seerfar/ozon/keywordBackSearch to call proxy_call. Read query/queryCn, search market metrics, and dimension.type、dimension.naturalRank、dimension.exposure、dimension.conversion；type:["0"] for organic keywords,type:["1"] for ad keywords.skuIds holds at most 20,skuIds、hasVariant、page are all required.

4. Store product structure and bestsellers

{
  "id": 1362816,
  "page": {"page": 1, "pageSize": 20, "orders": [{"field": "sales", "direction": "DESC"}]}
}

Use toolName=seerfar/ozon/shopSearch to call proxy_call. First display store-level totalSales、totalRevenue、productCount、dailySales、rating and delivery distribution, then display products' sku、price、sales、reviewRating、sellerType、fulfillment。pageSize is at most 20; a negative store ID may represent Ozon self-operated, whenreturnCancellationRate is missing, display -。

5. Category capacity and historical months

{
  "categoryId": "15621032_15621049_115951147",
  "date": "2026-02",
  "fulfillment": "FBO",
  "page": {"page": 1, "pageSize": 20, "orders": [{"field": "revenue", "direction": "DESC"}]}
}

Use toolName=seerfar/ozon/categorySearch to call proxy_call. First read categoryInfo、totalSales、totalRevenue、avgPrice、rating、seasonalityAmplitude、seasonalityCoef and the date range, then list product fields;fulfillment must be a single string, not an array,categoryId must be a Seerfar hierarchy ID.

6. Single SKU details and sales trend

{
  "sku": "175924376",
  "dateRange": "past_90_days"
}

Use toolName=seerfar/ozon/productDetailSearch to call proxy_call. Read title、sku、price、reviewRating、totalSales、dailySales、totalRevenue、stock、categoryRanks、salesTrendVOList、sellerName、brandName and fulfillment; summarize the trend by peak, direction, and window, and read the full daily series from the current MCP response. This interface queries only one SKU per call; sales/sales amount are model estimates for the selected window.

7. Multi-metric product report filtering

{
  "page": {"page": 1, "pageSize": 20, "orders": [{"field": "sales", "direction": "DESC"}]},
  "monthlySales": {"min": 5000},
  "price": {"max": 500},
  "convToCartPdp": {"min": 1},
  "returnCancellationRate": {"max": 10},
  "fulfillment": ["FBO"]
}

Use toolName=seerfar/ozon/productReportSearch to call proxy_call. Read sku/title/price/sales/revenue/reviewRating/reviewCount/brandName/sellerName/fulfillment as well as growth, conversion, gross margin, and return metrics;data and products are the same set of products, do not double-count alias fields.skus if used, at most 10 per call.

Display rules

Objective presentation: clearly display raw metrics, query conditions, time window,total、costToken and interface status in tables or sections; do not directly package the data into guaranteed returns or deterministic product-selection conclusions.
Label granularity and source: clarify whether the current result is at keyword, product, store, or category granularity, and label the corresponding endpoint/Seerfar data source; for consecutive queries, label the source and time window item by item.
Preserve Russian and platform information: for keywords, preferentially display the query original text and attach queryCnwhen a value exists; keyword results also display platform(0=Ozon, 1=Wildberries). For reverse lookup, also display dimension.type(0=organic, 1=ad) and ranking/impressions/conversion.
Currency and units：price、revenue、totalRevenue etc. are labeled as Russian rubles per the interface ₽; sales volume is in units, rating is on a 0–5 scale, ratios/growth rates carry % or an explicit 0–1 ratio, weight is in g, volume is in L.
Avoid alias duplication: in product reports productId=sku、monthlySalesUnits=sales、monthlySalesRevenue=revenue、rating=reviewRating、brand=brandName、productPageUrl=productUrl; for categories/stores also preferentially choose one set of raw fields to display.
Summary and pagination: for stores/categories, first display the global summary, then display the current page of products; whenhasNextPage=true , prompt that you can continue via page.page , and pageSize No more than 20. For large results, display only the necessary rows and the count; do not stuff the full array directly into the context.
Time and trends: market keyword searchDate, reverse lookup historyDate, category date, and detail dateRange have different semantics; when displaying, state the actual data window; for a single product, salesTrendVOList summarizes the peak and direction, andsales:0 indicates no sales rather than missing data.
Missing values and empty results: fields defined in the schema but missing from the response are shown as - or N/A; for store/category/detail, an empty total=0 result should indicate that the ID may be wrong; do not falsely report a system failure. Store sellerType is a local/cross-border flag, whereas the category-level sellerType is a delivery-method count mapping; do not confuse the two.
API errors: when code is not "200" or errcode is not 200 , pass through the reason for msg/errmsg and give a targeted correction; for parameter errors, check required fields, IDs, date formats, and enum values; for1002 , check the page size; for rate-limit errors such as1003 , wait and then let the user decide whether to retry.
Authentication, fees, and disclaimers: handle 401/402 or balance-related prompts as described in the next section; display costToken, and remind about fees before the user frequently pages through results or runs multi-SKU/multi-condition queries; Seerfar metrics are for data analysis reference only and are not equivalent to the official Ozon backend or a commercial guarantee.

Resolve authentication and credit issues

MCP or proxy_call missing: stop business calls, configure according to references/onboarding.md and reload the client; do not use the HTTP fallback.
MCP connection 401: prompt the user to log in to WorkBuddy again, reload the connection, or contact the administrator; do not ask the user to fill in Authorization.
Downstream 401 after a successful proxy request: handle it as a WorkBuddy automatic authorization or downstream business authentication failure; do not pass credentials in arguments .
Downstream 402 or insufficient credits: guide the user to visit https://agent.linkfox.com/; do not automatically select a plan, place an order, pay, or poll.
403 and other errors are handled according to the corresponding API reference; do not misclassify them.

Credit consumption notes

Users pay fees due to credit consumption. Evaluate carefully: when this skill needs to be called frequently, or when the user does not anticipate the amount of credit consumption, be sure to remind the user and let the user decide whether to continue.