Skip to main content
Glama
woyaxnini

mcp-ozon-seller

by woyaxnini

Archive Product

archive_product

Hide products from Ozon storefront by archiving them. Archived products are not visible to buyers but can be restored using unarchive_product.

Instructions

Hide one or more products from the Ozon storefront (archive them). Archived products are not visible to buyers but are preserved and can be restored. Provide an array of product_ids. Use unarchive_product to restore.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
product_idsYesArray of Ozon product IDs to archive
Behavior4/5

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

Discloses that archived products are not visible to buyers but preserved and restorable. Without annotations, it covers the key behavioral trait. Could mention if it affects existing orders or listings, but not critical for this action.

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?

Two concise sentences, front-loaded with core action, no fluff. Every sentence adds value.

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?

Tool is simple (one param, no output schema). Description covers main functionality, restoration pointer, and usage. Minor gap: no mention of rate limits or auth, but not essential for this straightforward tool.

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 coverage is 100% for the single parameter. Description restates the schema's purpose ('array of product_ids') without adding new semantic detail. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it hides/archives products from Ozon storefront, distinguishing from unarchive_product. Verb 'archive' is specific and resource-oriented.

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

Usage Guidelines5/5

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

Explicitly says when to use (to hide products) and when not (use unarchive_product to restore). Also provides instruction to provide an array of product_ids.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/woyaxnini/mcp-ozon-seller'

If you have feedback or need assistance with the MCP directory API, please join our Discord server