Skip to main content
Glama
Ozon Consumer MCP

Ozon Consumer MCP

by errogaht

ozon_product_media

Read-onlyIdempotent

Collect all available product gallery photos and videos at their maximum observed resolution, returning media IDs, URLs, dimensions, and completeness without inventing hidden originals.

Instructions

Открыть галерею товара и собрать все доступные фотографии/видео в максимальном реально наблюдаемом разрешении. Возвращает mediaId, URL, размеры и полноту. Невидимые оригиналы не выдумывает.

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_product_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses the resolution ceiling ('максимальном реально наблюдаемом разрешении'), the returned fields (mediaId, URL, sizes, completeness), and the honesty constraint that hidden originals are not fabricated.

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 return shape and a limitation caveat. No filler; every sentence contributes distinct information.

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 no output schema, the description usefully summarizes return values and the non-fabrication guarantee, which is good. But for a two-parameter tool with zero schema documentation, the unexplained 'limit' and 'url' semantics leave an agent guessing how to invoke it correctly.

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

Parameters2/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, and it does not mention either parameter. The required 'url' and the 'limit' (1-100) cap are completely unexplained — nothing says whether limit caps photos, videos, or both, or what happens when 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?

The description states a specific verb and resource: open the product gallery and collect all available photos/videos at the maximum observable resolution. It is clearly distinguishable from siblings like ozon_media_import or ozon_review_media by its product-gallery scope, though it never names an alternative explicitly.

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?

Usage is only implied by the phrase 'Открыть галерею товара' — an agent can infer it is for gathering product media, but there is no explicit when-to-use, when-not-to-use, or pointer to ozon_media_get versus ozon_media_import. Guidance is adequate but leaves routing to inference.

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