Skip to main content
Glama

Yandex Market Search

yandex_search
Read-onlyIdempotent

Search Yandex Market for products to get current prices, ratings, sellers, and stock availability.

Instructions

Search Yandex Market and return products with both prices, ratings and sellers.

Yandex Market aggregates many sellers per product, which makes it the best single source for "what does this cost right now" across the Russian market — including goods Wildberries and Ozon do not carry.

Each result reports price_rub (what anyone pays — the price the SERP snippet's cart button charges, cross-verified against product cards) and price_with_plus (requires a Yandex Plus subscription, typically 25-30% lower). Prefer price_rub when quoting a price to a person; price_old_rub is the struck-through reference price and must never be quoted as the price.

A search row describes the SERP snippet's offer, which may be a different member of the product family than the offer yandex_card for the same product_id defaults to (live example: search shows REDMOND KM243 sku 4668084807 while the card for that id defaults to a KM245 offer at another price). The row is SERP-faithful — reconcile it with a card by sku_id, not by the product URL.

Note rating_count counts star ratings, not written reviews; the written count is available per product via yandex_card.

Return Format

YandexSearchResponse: {query, page, page_count, total_available, has_next_page, returned, items, meta}. Items carry product_id, sku_id, title, brand, seller, price_rub (everyday — None when absent, never 0), price_with_plus, price_old_rub (struck-through reference), currency, rating, rating_count, in_stock, is_express, url, image. Zero results is NOT an error — it is reported via meta.warnings. meta.extraction names the path: 'ssr' (full widget state), 'zone' (first-screen snippet payloads — both prices, no brand) or 'ld+json' (degraded, Plus price only).

Error Format

On validation or transport/parse failure, raises ToolError with a JSON message describing the error code and whether it is retryable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, 1-based.
limitNoMaximum products to return from the page.
queryYesFree-text search query in Russian, e.g. 'iphone 15' or 'стиральная машина узкая'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metaNo
pageNo
itemsNo
queryNo
returnedNo
page_countNo
has_next_pageNo
total_availableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, but the description adds substantial behavioral context: price semantics (price_rub vs price_with_plus, price_old_rub must never be quoted), SERP vs card discrepancies, rating_count vs written reviews, zero results handling, and extraction paths. No contradiction with annotations.

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 lengthy but efficiently organized with bold headers and dense, relevant information. Every section—purpose, price nuances, discrepancy warning, return format, error format—earns its place. It front-loads the core purpose and then provides critical caveats without fluff.

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

Completeness5/5

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

Given the tool's complexity (multiple price fields, extraction paths, error handling, reconciliation with yandex_card), the description covers all essential operational aspects. It explains return semantics beyond the output schema and handles edge cases like zero results and non-retryable errors. Nothing an agent needs to call it correctly is missing.

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% with descriptions for all three parameters (page, limit, query). The description does not add new parameter-level semantics; it focuses on output semantics and usage caveats. Baseline 3 is appropriate since the schema already documents parameters fully.

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 tool searches Yandex Market and returns products with prices, ratings, and sellers. It differentiates itself from siblings by highlighting Yandex Market's seller aggregation and its coverage of goods not on Wildberries/Ozon, making its purpose unmistakable.

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 positions the tool as the best source for current prices on the Russian market and advises preferring price_rub when quoting prices. It also warns about discrepancies between search rows and yandex_card, guiding correct usage. This is actionable guidance beyond mere existence.

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