yandex-market-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YM_PROXY | No | Proxy URL, e.g. http://user:pass@host:3128 (the city then follows the proxy's IP) | |
| YM_CACHE_DIR | No | Where the cookies (session.json, 0600; directory 0700) and the pause marker live | ~/.cache/yandex-market-mcp |
| YM_MIN_INTERVAL | No | Seconds between requests (never below 3). The IP is usually shared with your own browsing | 4.0 |
| YM_EXPECTED_REGION | No | Region id you expect Market to assign to your IP (213 Москва, 2 Санкт-Петербург). If the page says otherwise, answers carry a WARNING note — usually a VPN. It does not change the city: nothing can, without logging in | 54 |
| YM_CAPTCHA_COOLDOWN | No | After a captcha the server does not query the site for this many seconds, also across restarts | 1800 |
| YM_RATE_LIMIT_COOLDOWN | No | The same pause after HTTP 403 / 429 persisted through one retry | 600 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_productsA | Search Yandex Market like the site: real pages, the site's sort orders and a price window. Each item: offer/card/model/SKU ids, title, card URL, the three labelled prices (without the Pay card, with it, crossed-out), discounts, seller, sponsored flag, rating of this seller's card with its count, badges, cross-border / markdown flags, stock and delivery dates. One request per call. |
| get_productA | One seller's product card, live: the three labelled prices, promo conditions, delivery, seller. Also: rating of this seller's card with stars and a check whether the card pools other products, «Все N предложений от X» (X = lowest Pay-card price; list them with get_offers), badges with their real meaning, cross-border / markdown / version flags, stock, characteristics and question count. One request (three with include_seller_legal). |
| get_offersA | All sellers' offers of one product (the site's «Все N предложений»), as tiles. Market's server pages show the first 16 offers per sort and ignore |
| get_reviewsA | Buyer reviews with date, stars, pros, cons, comment, votes, photo count and the product each is about. The header numbers (rating, counts, stars) are the site's for the chosen scope; for scope="variant" the site still shows the whole card's numbers (labelled). Items without text are ratings only. Author names and order numbers are never returned. One request. |
| get_questionsA | Buyers' questions about a card with the answers shown on the site; Dates are exact. Names of buyers are never returned; greetings with a name in answers are masked. One request. |
| get_sellerA | A seller's storefront header (rating, ratings count, orders, years on Market, status) and legal entity. The legal entity (name, INN, OGRN, address, cross-border flag) comes from the site's seller-info popup, loaded with a POST to Market's /api/ (robots.txt Disallow) — two requests. |
| compare_productsA | Side-by-side rows for up to 10 seller cards: the three prices, rating of the card, seller, delivery. One request per card, sequentially (about 5 s each). A card that fails gets an |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct resource and action: search, single product card, all offers, comparison, reviews, questions, and seller info. Even the overlapping get_product and get_offers are clearly separated by scope (one seller vs. all sellers).
All tool names follow a consistent verb_noun snake_case pattern: search_products, get_product, get_offers, compare_products, get_reviews, get_questions, get_seller. No mixed conventions or vague verbs.
Seven tools is well-scoped for a marketplace research API. Each tool covers a distinct user need without redundancy or bloat.
The set covers the full product research lifecycle: discovery (search), deep dive (product, offers, compare), social proof (reviews, questions), and seller trust (seller info). No obvious dead ends or missing core operations for a read-only marketplace tool.