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

Linkfox Mpstats Ozon Product Detail

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

Fetch detailed Ozon product pages via MPStats to benchmark rival listings, review attributes, ratings, and price positioning while evaluating what to sell or how to differentiate.

About

Linkfox skill that retrieves detailed Ozon marketplace product data through MPStats so agents can analyze competitor listings, pricing, ratings, and attributes during early e-commerce validation.

  • Ozon product detail via MPStats
  • Competitor listing benchmarking
  • Price and attribute comparison
  • Marketplace intelligence for sellers
  • Structured rival SKU snapshots

Linkfox Mpstats Ozon Product Detail by the numbers

  • 253 all-time installs (skills.sh)
  • +36 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #525 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-product-detail

Add your badge

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

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

What it does

Fetch detailed Ozon product pages via MPStats to benchmark rival listings, review attributes, ratings, and price positioning while evaluating what to sell or how to differentiate.

Files

SKILL.mdMarkdownGitHub ↗

MPSTATS Ozon Product Detail (Batch)

This skill batch-fetches the full product card for one or more Ozon (Russia) SKUs via MPSTATS. Returned fields include price, Ozon Card price, discount, rating, reviews, stock, monthly sales units, monthly sales revenue, lost profit, potential revenue, first listing date, image, and more.

Core Concepts

Batch semantics: Pass up to 100 productIds in a single call. The server fans out concurrently and automatically retries each failed SKU once; partial success is allowed, so a mixed list is normal.

Fulfillment model per SKU: Each product card carries deliveryScheme:

  • FBO — Fulfillment by Ozon (stock in Ozon warehouses)
  • FBS — Fulfillment by Seller (seller-shipped)

Pass includeFbs: true to allow FBS SKUs and FBS-scoped metrics into the response; false (or omitted) keeps the result FBO-centric. This switch applies to the whole batch.

Previous-period comparison: The card includes previousSalesUnits / previousRevenue — sales and revenue from the equal-length period immediately before [startDate, endDate] — ready for MoM / period-over-period diffs without extra calls.

Revenue potential: revenuePotential projects what the SKU could have earned if it had been in stock every day of the window; compare with monthlySalesRevenue to quantify stock-out drag, together with lostProfit / lostProfitPercent.

Date window: startDate / endDate define the period for all period-aggregated metrics. Latest selectable date is yesterday (T-1); today and future dates are rejected.

Parameters

ParameterTypeRequiredDescription
productIdsarray<integer\string>yes
startDatestringnoStats window start, YYYY-MM-DD; latest = yesterday
endDatestringnoStats window end, YYYY-MM-DD; latest = yesterday
includeFbsbooleannotrue to include FBS data; false = FBO-only

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_product_detail.py directly for ad-hoc queries.

Usage Examples

1. Single-SKU detail

{"productIds": [1786874757]}

2. Batch lookup with period

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

3. FBO-only snapshot

{"productIds": [1786874757, 151623766], "includeFbs": false}

4. SKUs discovered upstream — full card

{"productIds": [<list from mpstats-ozon-product-search>]}

How to Chain with Other Ozon Skills

1. Search → detail: Use mpstats-ozon-product-search to resolve a keyword / brand / seller into productIds, then pass them here for full metrics. 2. Detail vs trend: This endpoint is a period aggregate per SKU; for day-by-day time-series on a single SKU, use mpstats-ozon-product-trend. 3. Detail vs drill-downs: When the input dimension is a brand / category / seller (not a SKU list), prefer brand-products / category-products / seller-products — they already return aggregated metrics per SKU under that dimension.

Display Rules

1. Compact table — lead with productId, title, price, monthlySalesUnits, monthlySalesRevenue, rating, reviewCount, balance, deliveryScheme, firstDate. Pull revenuePotential / lostProfit / lostProfitPercent in when the user asks about stock-out impact. 2. Currency — Ozon native currency is RUB; the currency field carries the symbol. Do not silently relabel. 3. Partial success — the response carries successCount / failedCount / failures; when failedCount > 0, list the failed productIds from failures to the user rather than silently dropping them. 4. Period-over-period — when both current and previous* fields are present, render them side-by-side or as diff; don't report a single-period number as "trend". 5. With-stock vs all-dayssalesPerDayWithStock / dailySalesRevenueWithStock only count days that had inventory; distinguish from the plain salesPerDay / dailySalesRevenue. 6. Delivery model — prefer the per-SKU deliveryScheme value over assuming FBO; remind users when a batch mixes FBO and FBS. 7. No business advice — present data; do not extrapolate "this SKU is worth selling" without a wider analysis.

Important Limitations

  • 100-SKU batch cap — split larger input lists and call multiple times; the Agent must paginate.
  • Ozon-only — this tool does not cover Wildberries or other Russian marketplaces.
  • T-1 dataendDate must not be today or future.
  • FBS coverage — some categories have partial FBS coverage; if the input set is FBS-heavy, expect sparser cards.
  • Field set differs from brand/seller — this endpoint does not return brandId, country, category, minPrice / maxPrice / averagePrice, balanceFbs, frozenStocks, warehousesCount, daysInSite / daysInStock / turnoverDays, position / categoryPosition / revenueSharePercent, isFbs. Use brand-products / category-products / seller-products if those are needed.
  • No translation — titles are returned in Russian; translate on demand when presenting to Chinese / English users.

User Expression & Scenario Quick Reference

Applicable — Per-SKU Ozon card lookup:

User SaysScenario
"Pull Ozon details for these SKUs"Batch card fetch
"What's the price / rating / stock of Ozon SKU 1786874757"Single-SKU card
"Competitor's Ozon listings, give me sales & rating"Competitor card audit
"Compare FBO vs FBO+FBS metrics for this SKU set"Fulfillment-model comparison

Not applicable — Needs beyond per-SKU card:

  • Keyword-based discovery → use mpstats-ozon-product-search
  • Day-by-day time-series for one SKU → use mpstats-ozon-product-trend
  • Listing copy / reviews / images analysis beyond URL → out of scope
  • Brand / category / seller drill-down with filters → use the matching drill-down skill

Boundary judgment: If the user already has a SKU list and wants per-SKU sales / price / stock / rating, this is the skill. If they don't yet have SKUs, route through the search or drill-down skills first.

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_product_detail.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.