Ozon Consumer MCP

Overview Schema Source Related Servers Discussions Admin

ozon_collection_create

Create Ozon product collections with a defined name, description, cover media, visibility, and initial product URLs; preview changes by default and apply them only when explicitly confirmed.

Instructions

Создать подборку с точным названием, описанием, обложкой coverMediaId, isPublic и начальными productUrls. По умолчанию preview; apply=true выполняет по поручению владельца. Публичность не выбирается автоматически.

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": {
      "name": "<name>",
      "isPublic": "<isPublic>"
    },
    "name": "ozon_collection_create"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`apply`	No
`isPublic`	Yes
`description`	No
`productUrls`	No
`coverMediaId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety baseline is covered. The description adds real value with the dry-run default and the delegation note ("по поручению владельца"), plus the warning that publicness is never inferred. It does not say what a preview returns or whether a follow-up confirm step is needed.

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?

Three dense sentences with no filler, front-loading the create semantics before the preview/apply nuance. Slightly telegraphic phrasing (embedded field names without articles) is efficient rather than wasteful.

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 write tool with six undocumented parameters and no output schema, the definition covers the main fields and the preview default, but leaves the preview result and any confirm/status follow-up unexplained despite confirm and status siblings existing. An agent could call it, but would have to discover the post-call flow by trial.

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 name every one of the six parameters and explains apply's preview/execute split and that isPublic must be chosen explicitly. However, constraints present only in the schema (name maxLength 100, productUrls maxItems 100, coverMediaId maxLength 100) and the format of productUrls are not clarified, so it adds meaning but not enough to fully compensate.

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 and resource ("Создать подборку" — create a collection) and enumerates the fields it accepts: name, description, coverMediaId, isPublic, productUrls. An agent immediately knows this is a create operation, though no sibling (e.g. ozon_collections) is named to contrast against.

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?

It gives clear operational guidance: default is preview, and apply=true actually performs the creation on the owner's behalf. That is a genuine when-to-use rule for the execute path. It stops short of naming alternatives or stating when a preview is preferable to an immediate apply.

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