WB MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WB_API_KEY | Yes | Your Wildberries seller API key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_productsA | Возвращает список карточек товаров продавца из Wildberries Content API. Параметры limit и offset работают как в классической пагинации. |
| get_product_reviewsA | Возвращает отзывы покупателей на товар по его nmId из Wildberries Feedbacks API. |
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 2 tools
The two tools are clearly distinct: one retrieves product cards, the other retrieves customer reviews for a specific product. There is no overlap in purpose or target resource.
Both tools follow a consistent 'get_<plural_noun>' pattern, making the naming predictable and uniform.
With only two tools, the set feels minimal but not unreasonable for a narrow product-and-reviews scope. However, given the generic 'WB MCP Server' name implying broader Wildberries coverage, two tools is on the thin side.
The server exposes only read operations for products and reviews, with no coverage of other common Wildberries seller resources (orders, stocks, prices, etc.) and no lifecycle operations. Significant gaps exist for any seller-facing workflow beyond basic listing and review retrieval.