Skip to main content
Glama

Ozon Product Reviews

ozon_reviews
Read-onlyIdempotent

Fetches Ozon product review texts, scores, helpfulness votes, and star distribution, paging through results and deduplicating by UUID. Use it to inspect customer feedback and rating breakdowns.

Instructions

Fetch Ozon product review texts + star distribution via composer-api.bx.

Tier-1 (curl_cffi) tried first, Tier-2 (Chrome CDP) fallback — same path as ozon_card. Returns review texts (comment/positive/negative), per-review score, helpfulness votes, date, plus the overall star distribution and total count.

Pages are walked automatically (30/page) until limit texts are collected or pages run out, deduplicating by review uuid. Hard cap of 10 pages.

Reviews are pooled per card family, not per product

Ozon shows one shared pool for every variant of a card, and those variants are frequently different products — different wattage, different brand. So rating_score and distribution describe the POOL, not the SKU asked for. Each review carries item_id, the SKU it is really about; own_reviews counts the returned reviews whose item_id matches requested_item_id, and pool_variants names every SKU in the pool. Filter by item_id before drawing any conclusion about a product, and say so when own_reviews is 0 — a headline 4.8 can be borrowed entirely from neighbours.

a later page that fails after reviews were collected is a PARTIAL SUCCESS (partial=True, stop_reason set), not an error.

Full field list and error codes: guide://ozon/ozon_reviews.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sku_or_path": "<sku_or_path>"
    },
    "name": "ozon_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoReview ordering. Aliases: "recent"/"default" -> Ozon's new-and-helpful order (not strict chronology), "best"/"highest" -> highest rated first, "worst"/"lowest"/"complaints" -> LOWEST rated first. Raw API values usefulness_desc/score_desc/score_asc also accepted.recent
limitNoMax review texts to return (1..100). Distribution+total always full.
sku_or_pathYesSKU integer-as-string, full Ozon URL, or /product/<digits>/ path. Normalized to /product/<digits>/reviews/ (SSRF-allowlisted).

Output Schema

NameRequiredDescriptionDefault
urlNo
sortNo
_metaNo
statusNo
partialNo
reviewsNo
returnedNo
tier_usedNo
last_errorNo
own_reviewsNo
stop_reasonNo
distributionNo
rating_scoreNo
pages_fetchedNo
pool_variantsNo
reviews_countNo
requested_limitNo
requested_item_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.9.1
    • changedInput schema / properties / sort / description
      Previous value: -"Review ordering. Aliases: \"recent\"/\"default\" -> newest, \"best\"/\"highest\" -> highest rated first, \"worst\"/\"lowest\"/\"complaints\" -> LOWEST rated first. Raw API values published_at_desc/score_desc/score_asc also accepted."New value: +"Review ordering. Aliases: \"recent\"/\"default\" -> Ozon's new-and-helpful order (not strict chronology), \"best\"/\"highest\" -> highest rated first, \"worst\"/\"lowest\"/\"complaints\" -> LOWEST rated first. Raw API values usefulness_desc/score_desc/score_asc also accepted."
  2. Changed3 schema fields changedv2.1.0
    • addedOutput schema / properties / own_reviews
      Added value: +{}
    • addedOutput schema / properties / pool_variants
      Added value: +{}
    • addedOutput schema / properties / requested_item_id
      Added value: +{}
  3. First observedv1.5.1

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover safety (readOnly, idempotent, non-destructive), yet the description adds substantial behavior: Tier-1 curl_cffi with Tier-2 Chrome CDP fallback, 30-per-page walking, dedup by review uuid, a 10-page hard cap, and partial-success semantics. The pooled-per-card-family warning is a genuinely non-obvious trait that would otherwise cause misreading of rating_score and distribution.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then organized under a clear heading for the pooled-reviews caveat. Dense but every section carries decision-relevant information; the only mild cost is length from the multi-line transport and pagination detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paginated, fallback-driven scraper with an output schema, the description covers everything an agent needs: transport behavior, pagination limits, dedup, partial-success handling, and the critical interpretation caveat about pooled reviews. Return field details are deferred to the guide reference, which is appropriate given the output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning about limit: pages are walked automatically until that many texts are collected, while distribution and total remain full. It does not elaborate on sort aliases, but the schema already documents those thoroughly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource: 'Fetch Ozon product review texts + star distribution via composer-api.bx.' It names the exact data returned and implicitly separates itself from ozon_card (card data) and wb_reviews (different marketplace) by naming the Ozon review domain and the shared transport path.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operational guidance: filter by item_id before drawing conclusions, and state when own_reviews is 0. It also explains that a failed later page is a partial success rather than an error. It stops short of explicitly naming a sibling to use instead when the agent wants card metadata rather than reviews.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.