Yandex Market Seller MCP Server

ym_prices

Read-only

Retrieve current product prices and currency at the business level for Yandex Market seller pricing.

Instructions

Get product prices at business level. Returns current prices, currency. Use ym_execute with action campaign_offers for campaign-level prices.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ym_prices"
  }
}

Input Schema

Name	Required	Description	Default
`offer_ids`	No
`page_token`	No
`limit`	No
`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

A3.9/5.0

Behavior4/5

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

Annotations already mark readOnlyHint=true, so the description's mention of 'Get' aligns with that. It adds context about returning current prices and currency, though it does not detail pagination or other behaviors. Still, with annotations covering safety, a 4 is warranted.

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 with no wasted words. Front-loaded with purpose and returns, then usage guidance.

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?

Despite having an output schema, the description lacks parameter explanations which are essential given 0% schema coverage. It does not mention pagination or filtering, leaving significant gaps for a 4-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description provides no explanation of the 4 parameters (offer_ids, page_token, limit, business_id). It fails to add any meaning beyond the schema's names and defaults.

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 clearly states the verb 'Get' and resource 'product prices at business level', and specifies that it returns current prices and currency. It also distinguishes itself from sibling tool ym_execute for campaign-level prices.

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 states when to use (business-level prices) and when not to (campaign-level), providing an alternative: 'Use ym_execute with action campaign_offers for campaign-level prices.'

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

Deploy Server