Skip to main content
Glama
Ozon Consumer MCP

Ozon Consumer MCP

by errogaht

ozon_media_get

Read-onlyIdempotent

Fetch a previously observed image by mediaId for external viewing; for video, return the source URL. Add analyze=true and a question to get Luna image analysis.

Instructions

Получить ранее наблюдаемое изображение по mediaId как MCP image для просмотра внешним агентом; для видео возвращает исходный URL. analyze=true дополнительно анализирует изображение Luna по question.

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": {
      "mediaId": "<mediaId>"
    },
    "name": "ozon_media_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
analyzeNo
mediaIdYes
questionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered; the description adds genuinely new behavior: the payload is returned as an MCP image for an external agent, video returns the source URL instead, and analyze=true triggers a Luna analysis pass. It does not mention failure modes (e.g. unknown mediaId) or latency/cost of the Luna call.

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?

A single tight sentence with the primary action first, branching clauses for video and for analyze=true separated by a semicolon. No filler or repetition; density is high but readable.

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?

With only 3 parameters and no output schema, the description covers the essentials of what is returned and the optional analysis mode. It still omits the origin of mediaId and the conditional relationship between analyze and question, which an agent needs to call it correctly.

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 parameter meaning; it does explain mediaId (identifier of previously observed media) and ties analyze=true to question-based Luna analysis. It leaves open where mediaId comes from, the accepted identifier format, and whether question is ignored when analyze is false or omitted.

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?

States a specific verb and resource ('Получить ранее наблюдаемое изображение по mediaId') and explains the dual return form (MCP image vs source URL for video). It does not name or contrast any sibling such as ozon_media_import or ozon_product_media, so it falls short of full differentiation.

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

Usage Guidelines3/5

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

The phrase 'ранее наблюдаемое' implies the media must already exist, and analyze=true is presented as an opt-in extension, which gives implicit usage context. However there is no explicit statement of when to use this instead of the other media siblings, and no exclusions or prerequisites.

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