Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
linkfox-ai avatar

Linkfox Mpstats Ozon Category Products

  • 258 installs
  • 64 repo stars
  • Updated August 3, 2026
  • linkfox-ai/linkfox-skills

Fetch Ozon category product rankings via MPStats to spot bestsellers, price tiers, and category entry opportunities.

About

LinkFox MPStats Ozon category products skill pulls ranked product data from Ozon categories through MPStats, helping sellers research demand, pricing tiers, and competitive density before entering the Russian marketplace.

  • MPStats Ozon category data
  • Bestseller identification
  • Category pricing bands
  • Russia marketplace scouting

Linkfox Mpstats Ozon Category Products by the numbers

  • 258 all-time installs (skills.sh)
  • +38 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #519 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/linkfox-ai/linkfox-skills --skill linkfox-mpstats-ozon-category-products

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs258
repo stars64
Last updatedAugust 3, 2026
Repositorylinkfox-ai/linkfox-skills

What it does

Fetch Ozon category product rankings via MPStats to spot bestsellers, price tiers, and category entry opportunities.

Files

SKILL.mdMarkdownGitHub ↗

MPSTATS Ozon Category Products

This skill drills into all Ozon (Russia) products under a given Russian category path, returning each SKU's sales, revenue, price, rating, stock, turnover, lost profit, and more. Designed for category bestseller mining, blue-ocean niche discovery, and brand-landscape scanning within a specific category.

Core Concepts

Russian full-path requirement: categoryPath must be the full Russian category path as used on the Ozon platform, with levels separated by / — for example, Одежда/Женская одежда/Футболки и топы женские. A partial path, English translation, or root-only value will generally return empty results.

Where to find the path: Typical workflows resolve the path via an upstream Ozon category-search step (if available in your toolchain) or by pulling a known SKU's category field from mpstats-ozon-product-detail / mpstats-ozon-product-search.

Filters are AND-combined: filters carries multi-field numeric conditions, each {field, op, value, value2?}. See the Filter Reference.

Currency: Default RUB. Override with currency (USD, EUR, CNY, ...) and optionally currencyRate.

FBO / FBS: includeFbs: true folds FBS into stock / sales numbers; false keeps FBO-only.

Parameters

ParameterTypeRequiredDescription
categoryPathstringyesFull Russian category path separated by /
startDatestringnoStats window start, YYYY-MM-DD; latest = yesterday
endDatestringnoStats window end, YYYY-MM-DD; latest = yesterday
pageintegernoPage number, starts at 1
pageSizeintegernoRows per page, 1-100, default 100
sortFieldstringnosnake_case column: sales, revenue, final_price, balance, rating, ...
sortDirectionstringnoasc / desc
currencystringnoCurrency code, default RUB
currencyRateintegernoCustom rate when non-default currency is used
includeFbsbooleannoInclude FBS data
filtersarraynoNumeric filter list (see below)

Filter Reference

Each filters entry: {"field": "<snake_case>", "op": "<OP>", "value": <num>, "value2": <num?>}.

Common fields: sales (monthly units), final_price (price RUB), rating (0-5), comments (reviews), balance (stock), revenue (amount RUB), days_in_stock, turnover_days, lost_profit, category_position.

Operators: GTE, LTE, GT, LT, EQ, NOT_EQ, BETWEEN (requires value2).

API Usage

This tool calls the LinkFox tool gateway API. See references/api.md for calling conventions, request parameters, response structure, and error codes. You can also execute scripts/mpstats_ozon_category_products.py directly for ad-hoc queries.

Usage Examples

1. Women's T-shirts — top by sales

{
  "categoryPath": "Одежда/Женская одежда/Футболки и топы женские",
  "sortField": "sales",
  "sortDirection": "desc",
  "pageSize": 100
}

2. Blue-ocean hunt (sales ≥ 50, rating ≥ 4.5)

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

3. Mid-price + strong turnover

{
  "categoryPath": "Электроника/Наушники",
  "filters": [
    {"field": "final_price", "op": "BETWEEN", "value": 1500, "value2": 5000},
    {"field": "turnover_days", "op": "LTE", "value": 30}
  ]
}

4. USD-converted ranking for cross-market comparison

{
  "categoryPath": "Электроника/Смартфоны",
  "currency": "USD",
  "sortField": "revenue",
  "sortDirection": "desc"
}

5. High lost-profit category scan

{
  "categoryPath": "Одежда/Мужская одежда/Куртки мужские",
  "filters": [{"field": "lost_profit", "op": "GTE", "value": 500000}],
  "sortField": "lost_profit",
  "sortDirection": "desc"
}

Display Rules

1. Compact category table — key columns: productId, title, brand, sellerName, price, monthlySalesUnits, monthlySalesRevenue, rating, balance, position, revenueSharePercent. 2. Revenue share = within this category query — 0-100%; clarify the basis when presenting. 3. Russian titles / brands — preserve original; translate on demand. 4. Currency labeling — state the currency; if converted, note "已按 USD 换算". 5. Pagination — report total; for large categories (tens of thousands of SKUs) suggest tightening filters rather than naively paging through. 6. Category position — lower is better; mention this when showing categoryPosition.

Important Limitations

  • Russian full path only — partial or translated paths return empty.
  • Path discovery is upstream — this endpoint does not browse the category tree; resolve the path via product detail / search first.
  • Page cap — max 100 rows per page.
  • T-1 dataendDate cannot be today or a future date.
  • No business advice — data-only view.

User Expression & Scenario Quick Reference

Applicable — Category-scoped Ozon product metrics:

User SaysScenario
"Bestsellers in category X on Ozon"Category bestseller mining
"Find blue-ocean SKUs in niche Y"Blue-ocean niche scan
"Show mid-price, fast-turnover items in this category"Multi-criteria niche filter
"Which brands dominate this Ozon category"Brand-landscape pre-cut (then group by brand client-side)
"Huge lost-profit opportunities in category X"Out-of-stock pain hunting

Not applicable — Needs beyond category drill-down:

  • Unknown category path → use mpstats-ozon-product-search or product detail to discover the exact Russian path
  • Brand-scoped drill → mpstats-ozon-brand-products
  • Seller-scoped drill → mpstats-ozon-seller-products
  • Single-SKU time-series → mpstats-ozon-product-trend
  • Wildberries / other Russian marketplaces → not covered

Boundary judgment: Use this skill when the dimension is a category path and you want the per-SKU roll-up under it. For cross-category comparisons you must run multiple calls and fuse results at the Agent layer.

Feedback:

Auto-detect and report feedback via the Feedback API when any of the following apply: 1. The functionality or purpose described in this skill does not match actual behavior 2. The skill's results do not match the user's intent 3. The user expresses dissatisfaction or praise about this skill 4. Anything you believe could be improved

Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.

<!-- LF_LARGE_RESPONSE_BLOCK -->

Handling Large Responses

To avoid overflowing the agent context, persist the response to disk and extract only the fields you need:

python scripts/response_io.py run --script scripts/mpstats_ozon_category_products.py --out-dir <DIR> '<params>'
python scripts/response_io.py read <file> --fields "<paths>"   # or --path "<JMESPath>"
Pick --out-dir outside any git working tree (e.g. /tmp/... on Unix, %TEMP%/... on Windows). Persisted responses may contain PII, pricing, or auth-sensitive data — do not commit them. Files are not auto-deleted; clean up when the task is done.

run writes the full response to a file and emits only a schema preview + file path. read projects specific fields, with --limit/--offset for slicing and --format json|jsonl|csv|table for output.

When to prefer this pattern — apply your judgment based on the response characteristics, e.g.:

  • High field count per record, or fields you don't need
  • Batch/paginated results (multiple items per call)
  • Long-text fields (descriptions, reviews, HTML, time series)
  • Output reused across later steps rather than consumed immediately

For small, single-use responses, calling the main script directly is fine.

⚠️ The preview is a truncated schema + sample, not the full data. Any field-level decision must read from the persisted file via read. <!-- /LF_LARGE_RESPONSE_BLOCK -->

--- For more high-quality, professional cross-border e-commerce skills, set [LinkFox Skills](https://skill.linkfox.com/).

Related skills

Automation & Workflowsecommercepricing

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.