Skip to main content
Glama

Yandex Market Product Card

yandex_card
Read-onlyIdempotent

Retrieve complete Yandex Market product details including price, discount, star-rating breakdown, and reviews with pros and cons. Input a product ID from search results.

Instructions

Fetch full detail for a Yandex Market product: prices, rating breakdown, reviews.

Two things here are hard to get anywhere else. The star distribution (rating_stars) shows whether a 4.8 average hides a cluster of one-star complaints. And reviews arrive with the card in one request, complete with pros, cons and helpfulness votes.

Reviews are capped at the ~13 Yandex renders server-side; the remainder load through an API this connector deliberately does not touch.

Return Format

YandexCardResponse: {product_id, sku_id, title, brand, seller, description, image, price_rub, price_with_plus, price_before_discount_rub, discount_percent, currency, offers_count, rating, rating_count, review_count, rating_stars, reviews, url, meta}. price_rub is None when the page has no usable price — never 0. Review items carry author, rating, date, pros, cons, comment, votes_up, votes_down, photos.

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
product_idYesNumeric Yandex Market product id — take it from yandex_search results.
include_reviewsNoInclude the server-rendered reviews (first ~13).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
metaNo
brandNo
imageNo
titleNo
ratingNo
sellerNo
sku_idNo
reviewsNo
currencyNo
price_rubNo
product_idNo
descriptionNo
offers_countNo
rating_countNo
rating_starsNo
review_countNo
price_with_plusNo
discount_percentNo
price_before_discount_rubNo
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses valuable behavioral traits: reviews are capped at ~13 server-side, the remainder load via an API deliberately not touched, price_rub is None when unavailable (never 0), and errors raise ToolError with retryability info. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections (Return Format, Error Format) and front-loaded purpose. The uniqueness pitch adds a bit of promotional framing and the return field list is lengthy, but each section provides practical value; could be tightened slightly without losing essential details.

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?

The description covers purpose, unique value, limitations (review cap), null semantics, error handling, and return format. Combined with rich annotations and an output schema, the agent has all necessary context to select and invoke this tool correctly.

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

Parameters4/5

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

Schema coverage is 100% with both parameters described. The description enriches include_reviews semantics by explaining the ~13 review cap and that the remaining reviews are deliberately not loaded via a secondary API, clarifying what the parameter actually controls.

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 opens with 'Fetch full detail for a Yandex Market product: prices, rating breakdown, reviews' – a clear verb+resource+scope. It distinguishes from siblings by highlighting unique data (star distribution, reviews included in one request) and notes these are 'hard to get anywhere else,' making the tool's 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 Guidelines4/5

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

Provides clear context for when to use (full detail, reviews, star distribution) and implies integration with yandex_search via the product_id parameter description ('take it from yandex_search results'). Does not explicitly name alternatives or exclusions, but the platform-specific name and sibling context make the intended use case obvious.

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/Vladimir-Human/ru-marketplace-mcp'

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