wildberries-mcp-ru

Overview Schema Source Related Servers Discussions Admin

wb_call_method

Read-only

Execute a read-only Wildberries API endpoint using its operation ID, supplying optional path, query, and body parameters to retrieve JSON data without altering any records.

Instructions

Execute one READ endpoint from the catalog by operation_id.

Target API: https://dev.wildberries.ru/en/openapi/api-information.

Reads only: nothing here changes data, so it runs without confirmation. To change data use wb_write_method, to delete use wb_delete_method.

Args: operation_id: id from the catalog (see wb_search_methods). path_values: values for {placeholders} in the path. query: query-string parameters. body: JSON request body (a few read endpoints take one). Returns JSON: {"ok": true, "status", "data"} or the error envelope.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`body`	No
`query`	No
`path_values`	No
`operation_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 15, 2026

removedInput schema / properties / confirm_write

Removed value: -{
-  "default": false,
-  "title": "Confirm Write",
-  "type": "boolean"
-}

removedInput schema / properties / i_understand_this_modifies_data

Removed value: -{
-  "default": false,
-  "title": "I Understand This Modifies Data",
-  "type": "boolean"
-}

First observedv0.5.3Sep 11, 2026

TDQS

A4.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=trueaiman, and the description reinforces this with 'nothing here changes data' and adds operational context not in annotations: 'it runs without confirmation.' It also discloses the return envelope and error case. This adds meaningful behavioral context beyond the structured annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded with the core purpose. Each sentence adds value: scope, target API, safety, arg explanations, and return format. There is no filler or unnecessary repetition.

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 read-only method with an output schema and clear annotations, the description covers operation selection, argument semantics, related tools, safety, and return envelope. It also gives the target API. An agent has everything needed to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden. It explains every parameter: operation_id as the catalog identifier, path_values for placeholders, query as query-string parameters, and body as the JSON request body. This fully compensates for the schema's lack of field descriptions.

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 specific verb-resource pair: 'Execute one READ endpoint from the catalog by operation_id.' It clearly distinguishes itself from write/delete siblings by stating what it does NOT do, and it references the catalog source. This leaves no ambiguity about the tool's core purpose.

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

Usage Guidelines5/5

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

The description explicitly says 'Reads only... To change data use wb_write_method, to delete use wb_delete_method,' naming the exact alternatives and the condition that selects them. It also points to wb_search_methods for obtaining operation_id. This is explicit when-to-use and when-not-to-use guidance.

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