Skip to main content
Glama
Ozon Consumer MCP

Ozon Consumer MCP

by errogaht

ozon_reviews

Read-onlyIdempotent

Retrieve full Ozon product reviews with text, pros and cons, ratings, author/date/variant, media, replies, and votes; filter by current variant or full group, sort, and paginate with cursor.

Instructions

Отдельные полные отзывы: текст/достоинства/недостатки, звёзды, автор/дата/вариант, фото/видео, ответы и голоса. По умолчанию scope=current: только «Этот вариант». scope=all явно включает всю группу. Если фильтр не подтверждён, отзывы не выдаются. Сортировка useful/new/rating_asc/rating_desc. Продолжайте nextCursor до конца; coverage отражает полноту.

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": {
      "url": "<url>"
    },
    "name": "ozon_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
sortNo
limitNo
scopeNocurrent
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds non-obvious behavior beyond them: the filter-confirmation gate that blocks output, the scope default and its effect on result breadth, and the coverage field signalling completeness. It stops short of describing the response object in detail, which matters somewhat because there is no output schema.

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?

Dense and front-loaded: what is returned, then scope semantics, then the filter precondition, then sort, then pagination. Every sentence adds new information, though the filter sentence is terse enough to be ambiguous about which filter is meant.

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

Completeness3/5

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

Covers the behaviorally difficult parts (gate condition, scope default, pagination completion) well for a 5-parameter tool with no output schema. However, the single required parameter is never explained, and with 0% schema coverage that leaves an agent guessing what `url` should point at.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry the load. It does explain scope (current vs. all), the four sort values, and cursor's nextCursor paging loop, but leaves the required `url` parameter and the `limit` bound (1-50) completely undefined.

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+resource in 'Отдельные полные отзывы' (individual full reviews) and enumerates the payload (text/pros/cons, stars, author/date/variant, photos/videos, replies, votes), which distinguishes it from sibling tools like ozon_review_media or ozon_questions without opening any schema.

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 real usage conditions: default scope=current vs. explicit scope=all for the whole group, a required confirmed filter before results are returned, and the need to keep paging with nextCursor. It does not name which sibling to use instead (e.g. the filter or confirmation tool), so the alternative-path guidance is implied rather than explicit.

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