Skip to main content
Glama

Yandex Market Product Card

yandex_card
Read-onlyIdempotent

Fetch full Yandex Market product details in one request: prices, star rating distribution, and reviews with pros and cons. Reveals whether a high average hides one-star complaints.

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.

price_rub is the explicit everyday price (null when the card carries only a conditional price) — never 0; price_with_plus requires paying with Yandex Pay (earlier Yandex Plus) and never ranks.

Full field list and error codes: guide://yandex/yandex_card.

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": {
      "product_id": "<product_id>"
    },
    "name": "yandex_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesNumeric Yandex Market product id — take it from yandex_search results.
include_reviewsNoInclude the server-rendered reviews (first ~13).

Output 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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses real behavioral traits: reviews arrive inline in one request but are capped at the ~13 Yandex renders server-side, and the remainder exist behind an API 'this connector deliberately does not touch.' It also explains price semantics (price_rub null when only a conditional price exists, never 0; price_with_plus requires Yandex Pay) and points to a guide resource for field lists and error codes.

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?

Front-loaded with the core purpose sentence, and the two-value-add highlights are grouped logically with a closing pointer to the guide resource. It is slightly verbose, spending sentences on return-field semantics (price_rub, price_with_plus) that an existing output schema likely already covers.

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?

For a two-parameter read tool with annotations and an output schema, this is complete: it covers what is returned, the review truncation limit, the deliberate absence of an extended-reviews path, price-field edge cases, and where to find the full field list and error codes.

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%, so both parameters are already documented and the baseline would be 3. The description still adds meaning to include_reviews by explaining the ~13-review server-side cap, which tells the agent the flag's effective ceiling and why it cannot retrieve more.

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 a concrete verb and resource: 'Fetch full detail for a Yandex Market product: prices, rating breakdown, reviews.' It names the platform explicitly (Yandex Market) and the payload contents, which distinguishes it from the *_card siblings for other marketplaces and from yandex_search by scoping it to a single product's full detail.

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

Usage Guidelines3/5

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

Usage is only implied: 'full detail' suggests calling it after a search, and the schema note that product_id comes from yandex_search results supplies the sequencing, but that guidance lives in the schema rather than the description. There is no explicit when-not guidance or naming of alternatives (e.g. yandex_search vs. a dedicated reviews tool), leaving the agent to infer routing.

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