Yandex Market Seller MCP Server

ym_order

Read-only

Retrieve complete order details: items, delivery, buyer info, and status history. Combine with order search tools to find specific orders.

Instructions

Get full order details: items, delivery, buyer info, status history. Use ym_orders to search/filter multiple orders.

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": {
      "order_id": "<order_id>"
    },
    "name": "ym_order"
  }
}

Input Schema

Name	Required	Description	Default
`order_id`	Yes
`campaign_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Jun 24, 2026

TDQS

A4.1/5.0

Behavior3/5

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

The description does not contradict the readOnlyHint annotation. It adds some behavioral context by listing the categories of details included, which is beyond what the annotation provides. However, it does not disclose any additional traits such as data freshness, rate limits, or prerequisites.

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?

The description is two sentences long, front-loads the purpose, and immediately follows with usage guidance. Every word serves a purpose, making it concise and well-structured.

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?

Given the tool's simplicity (2 parameters, has output schema), the description adequately covers the tool's purpose and usage context. The lack of parameter explanation is a minor gap, but the output schema handles return values.

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?

The schema description coverage is 0%, and the description does not explain the parameters (order_id, campaign_id) beyond what their names imply. It omits details such as campaign_id being optional with a default of 0, which would help the agent invoke the tool correctly.

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?

The description starts with 'Get full order details', clearly stating the verb and resource. It lists the types of details (items, delivery, buyer info, status history) and distinguishes from the sibling tool ym_orders by noting that ym_orders is for searching/filtering multiple orders.

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?

The description explicitly tells when to use this tool (to get full order details) and when to use the alternative (ym_orders to search/filter multiple orders). This provides clear guidance on tool selection.

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

Deploy Server