Skip to main content
Glama
Ozon Consumer MCP

Ozon Consumer MCP

by errogaht

ozon_media_import

Imports owner-selected PNG/JPEG/WebP files from the restricted Ozon MCP uploads folder for a cover, review, or return, and returns a mediaId for later upload.

Instructions

Импортировать выбранное владельцем PNG/JPEG/WebP для обложки, отзыва или возврата. Файл должен находиться в ~/.local/share/ozon-mcp/uploads; произвольные локальные файлы не читаются. Возвращает mediaId для явной последующей загрузки.

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": {
      "path": "<path>"
    },
    "name": "ozon_media_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

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?

Annotations already state readOnly=false, idempotent=false, destructive=false, so the safety profile is covered. The description adds genuinely new behavioral facts: the sandboxed uploads directory, the refusal to read arbitrary local files, and the non-obvious fact that this is a two-phase import that yields a mediaId rather than completing an upload. It stops short of noting the operations that consume the mediaId, which is why it is not a 5.

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, then the input constraint, then the return contract. Every sentence carries distinct information and none restates the annotations or schema verbatim.

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

Completeness4/5

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

For a one-parameter, non-idempotent import tool with no output schema, the description covers the action, the accepted formats, the location restriction, and the return value (mediaId) plus the deferred-upload implication. Missing are size limits and the name of the step that consumes mediaId, but nothing essential for a correct first call is absent.

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 0% and the single 'path' parameter has no description, so the description must compensate. It does so meaningfully by constraining the value domain: accepted formats (PNG/JPEG/WebP) and a mandatory location under ~/.local/share/ozon-mcp/uploads. It does not state whether 'path' is an absolute path or a filename relative to that directory, which keeps it from a 5.

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 opens with a specific verb+resource ('Импортировать ... PNG/JPEG/WebP') and scopes it to three concrete use cases (cover, review, return). It also clarifies that this tool stops short of uploading ('Возвращает mediaId для явной последующей загрузки'), which distinguishes it from a full upload step. It does not name a sibling explicitly, so it falls short of 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 Guidelines3/5

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

Usage context is implied through the enumerated targets (cover/review/return) and a hard precondition (file must live in ~/.local/share/ozon-mcp/uploads). However, there is no explicit 'use this instead of X' guidance and no statement about what to do after receiving mediaId, leaving the agent to infer the follow-up step.

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