ru-marketplace-mcp

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.

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.