Skip to main content
Glama
Ozon Consumer MCP

Ozon Consumer MCP

by errogaht

ozon_review_media

Read-onlyIdempotent

Open the photo/video gallery for a previously read review by review ID, confirming author, date, and text so only that review's media are returned.

Instructions

Открыть галерею конкретного ранее прочитанного отзыва по reviewId из 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": {
      "reviewId": "<reviewId>"
    },
    "name": "ozon_review_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
reviewIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new behavioral detail beyond them: it cross-checks author/date/text and guarantees it will not return photos belonging to a different review, which is a strong anti-hallucination promise for an agent gathering evidence. It does not say what happens when the cross-check fails (error vs. empty result), leaving one meaningful gap.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action, followed by the verification behavior and then the negative guarantee. Every sentence contributes a distinct piece of information with no repetition or filler.

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?

For a two-parameter, read-only tool with no output schema, the core intent and result type (large photo/video sources) are covered. But the undocumented limit parameter and the unspecified outcome when author/date/text verification fails leave real questions an agent would need answered before relying on the response.

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 carries the burden. It does add provenance meaning for reviewId (the value originates from ozon_reviews), which the schema pattern alone does not convey. However, the limit parameter (1-100) is never mentioned, so an agent gets no idea whether it caps returned photos/videos or something else.

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

Purpose4/5

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

The description states a specific verb and resource — opening the media gallery of one specific review — and anchors the identifier to a specific sibling (reviewId comes from ozon_reviews). It also adds a negative scope statement ('does not substitute photos from another review') that pins down what the tool will not do. It stops short of distinguishing itself from other media siblings such as ozon_media_get or ozon_product_media, which keeps it below a 5.

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?

Usage is framed as a prerequisite chain: the review must have been read previously, and reviewId must come from ozon_reviews. That tells an agent when this tool is applicable. It gives no explicit when-not conditions or named alternatives for plain media fetching, so it is clear context rather than full routing guidance.

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