Skip to main content
Glama
Ozon Consumer MCP

Ozon Consumer MCP

by errogaht

ozon_favorite

Saves an Ozon product to favorites, wishlist, or a specified collection; previews by default and applies changes only when confirmed.

Instructions

Сохранить товар в favorites, wishlist или collection. Для конкретной подборки/вишлиста укажите listName (collectionName — совместимый вариант). Уже сохранённое не удаляет. apply=true — выполнить по поручению; иначе preview.

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>",
      "target": "<target>"
    },
    "name": "ozon_favorite"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
applyNo
targetYes
listNameNo
collectionNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false but say nothing about the preview/execute split. The description adds that the default is a preview and that apply=true performs the action, and it reassures that already-saved items are not deleted, which is real behavioral context beyond the annotations. It does not explain what the preview returns or permission/auth requirements, so 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.

Conciseness4/5

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

Four short sentences, front-loaded with the action and destination, then narrowing to parameter conditions. No filler, though the alias note and the apply note are compressed into telegraphic fragments that could read ambiguously to a non-Russian model.

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 5-parameter mutation tool with no output schema, the description covers the essential decision points: destination selection, list naming, and dry-run versus execution. Remaining gaps are the return shape of preview mode and precedence between the two name parameters, which are minor but not negligible.

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 description coverage is 0%, so the description must carry the load, and it largely does: it explains target through the three destinations, documents listName and its collectionName alias, and defines apply's preview-versus-execute semantics. The url parameter is only implied by 'товар' with no format hints, and it does not say what happens if both listName and collectionName are supplied.

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 concrete verb plus resource: save a product into favorites, wishlist, or collection. The three destination values map directly to the target enum, so an agent can distinguish this from creation-oriented siblings like ozon_collection_create. It stops short of naming an explicit sibling it is not, which keeps it at 4 rather than 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?

Gives conditional guidance the agent actually needs: use listName for a specific collection/wishlist, and set apply=true to execute versus leaving it for preview. There is no explicit statement of when a different tool (e.g. ozon_collections or ozon_collection_create) should be used instead, so the routing guidance is context-only.

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