Yandex Market Seller MCP Server

ym_prices_update

Updates product prices on Yandex Market using a JSON array of offer IDs and price values. Supports business-level operations.

Instructions

Update product prices. Args: prices_json — JSON array of {offerId, price {value, currencyId}}. Business-level operation.

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": {
      "prices_json": "<prices_json>"
    },
    "name": "ym_prices_update"
  }
}

Input Schema

Name	Required	Description	Default
`prices_json`	Yes
`business_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

C2.7/5.0

Behavior2/5

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

The annotation already indicates it's a write operation (readOnlyHint=false). The description adds no further behavioral context like authorization needs, side effects, or rate limits.

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?

The description is very short with one sentence and a parameter note. It avoids unnecessary words, but the conciseness comes at the expense of completeness.

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

Completeness2/5

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

For a write operation, the description omits expected return values, prerequisites, and error scenarios. The presence of an output schema reduces the burden slightly, but the description should still provide context.

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?

Schema description coverage is 0%. The description adds format details for 'prices_json' (JSON array with specific fields) but does not mention 'business_id' at all, leaving its purpose unclear.

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 clearly states 'Update product prices' as a specific action on a specific resource. It differentiates from sibling 'ym_prices' which is likely for reading. However, it doesn't explicitly distinguish from other update tools like 'ym_stocks_update'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. The phrase 'Business-level operation' is vague and doesn't help the agent decide.

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

Deploy Server