Yandex Market Seller MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YM_TOKEN | Yes | API-ключ или OAuth-токен (обязательно) | |
| YM_TIMEOUT | No | Таймаут HTTP-запросов в секундах | 30 |
| YM_AUTH_TYPE | No | Тип авторизации: 'api-key' или 'oauth' | api-key |
| YM_BUSINESS_ID | Yes | ID бизнеса (обязательно) | |
| YM_CAMPAIGN_ID | Yes | ID кампании (магазина) (обязательно) | |
| YM_FILE_TIMEOUT | No | Таймаут файловых операций в секундах | 60 |
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 |
|---|---|
| ym_searchA | Find available actions by intent. Optional domain filter: orders, offers, prices, stocks, shipments, returns, feedbacks, chats, reports, bids, outlets, campaigns, geo, categories, warehouses, promos, quality, tariffs, supply, operations, delivery, logistics. Returns action ID, description, and JSON Schema of parameters. |
| ym_executeA | Execute action by ID. params_json validated against action schema. Use ym_search to discover actions and their schemas first. |
| ym_execute_fileC | Execute action that downloads a file (PDF/binary). output_path must be under ~/... or /tmp/... |
| ym_campaignsA | List all campaigns (shops) in the account. Returns array of {id, domain, placementType}. Use ym_campaign for details of a single campaign. |
| ym_ordersA | List orders with optional status filter. Statuses: UNPAID, PROCESSING, DELIVERY, PICKUP, DELIVERED, CANCELLED. Returns paginated list. Use ym_order for single order details. |
| ym_orderA | Get full order details: items, delivery, buyer info, status history. Use ym_orders to search/filter multiple orders. |
| ym_order_statusA | Update order status. Typical flow: PROCESSING → DELIVERY → DELIVERED. Args: status, substatus (optional). Use ym_execute with action order_status_batch for multiple orders. |
| ym_offersA | List products (offer mappings) at business level. Returns SKU, name, category, mapping status. Paginated. Use ym_execute with action campaign_offers for campaign-level offers. |
| ym_stocksA | Get product stocks for a campaign. Returns warehouse stocks per SKU. Use ym_execute with action stocks_update to change stock quantities. |
| ym_stocks_updateC | Update product stocks. Args: stocks_json — JSON array of {sku, warehouseId, items: [{count, type, updatedAt}]}. |
| ym_pricesA | Get product prices at business level. Returns current prices, currency. Use ym_execute with action campaign_offers for campaign-level prices. |
| ym_prices_updateC | Update product prices. Args: prices_json — JSON array of {offerId, price {value, currencyId}}. Business-level operation. |
| ym_returnsA | List returns for a campaign. Paginated. Use ym_execute with action return for single return details. |
| ym_shipmentsA | List first-mile shipments. Use ym_execute with action shipments_search for advanced filtering. |
| ym_feedbacksA | Get product reviews/feedbacks. Paginated. Use ym_execute with action feedback_comments for comments on a review. |
| ym_chatsA | List buyer chats. Use ym_execute with action chat_history for messages, chat_send to reply. |
| ym_bidsA | Get current bids at business level. Use ym_execute with action bid_recommendations for suggested values, bids_update to change. |
| ym_report_generateB | Start async report generation. Returns reportId for polling with ym_execute action report_status. Types: united-netting, united-marketplace-services, united-orders, united-returns, goods-realization, stocks-on-warehouses, goods-movement, shows-sales. |
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 18 tools
Each tool has a clear, distinct purpose. Overlapping tools like ym_order/ym_orders and ym_prices/ym_prices_update are differentiated by singular/plural or update suffix, preventing confusion.
All tools follow the consistent pattern 'ym_<noun>' or 'ym_<noun>_<verb>' (e.g., ym_campaigns, ym_order_status, ym_stocks_update). No mixing of conventions.
18 tools cover the full scope of a seller marketplace (orders, offers, prices, stocks, shipments, returns, feedbacks, chats, bids, reports). Each tool adds value without bloat.
The tool set covers most essential operations for a seller (CRUD on orders, prices, stocks, etc.). Minor gaps exist (e.g., no direct tool for creating campaigns/offers), but these can be fulfilled via ym_execute actions.