Skip to main content
Glama

Wildberries API: чтение (read-only)

wb_get
Read-only

Call any read-only Wildberries API method by ID to retrieve diagnostics, reports, lists, stock, and reviews without confirmation. Use it for non-changing requests; use wb_call for modifications.

Instructions

Вызвать READ-ONLY метод Wildberries API по id. Используй этот инструмент для любых чтений (диагностика, отчёты, списки, остатки, отзывы) — он не требует подтверждения и работает с токеном «Только чтение». Параметры path/query/header — в "params", тело — в "body". Для изменяющих методов используй wb_call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "wb_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesid read-only метода из wb_search
bodyNoТело запроса для POST read-only методов (JSON)
paramsNoИменованные параметры метода (path/query/header) — имена и типы смотри в wb_describe
accountNoИмя аккаунта, если настроено несколько токенов

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

The description adds real behaviour beyond readOnlyHint/openWorldHint: no confirmation prompt is required and it works with a read-only-scoped token, which is operationally valuable context. It is silent on rate limits, error behaviour, and what a successful response looks like, so it stops short of fully covering a generic proxy tool.

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?

Four short sentences, each doing distinct work: purpose, when to use, how to shape the call, and which sibling handles the opposite case. Purpose and scope are front-loaded with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter proxy endpoint with nested params and no output schema, the description covers invocation mechanics and the safety profile well. The remaining gap is that it never indicates the shape or volatility of the returned data, which matters when no output schema exists.

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

Parameters3/5

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

Schema coverage is 100%, so parameter meaning is already carried by the schema, and the description merely restates the split (path/query/header into "params", body into "body"). It adds no resolution guidance beyond the schema's pointer to wb_describe for names and types.

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 names a specific operation type and resource — invoking a Wildberries READ-ONLY API method by id — and explicitly carves out the boundary against wb_call for mutating methods. An agent can distinguish it from every listed sibling without opening the schema.

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?

It states the use case directly ("для любых чтений (диагностика, отчёты, списки, остатки, отзывы)") and names the alternative for the opposite case ("Для изменяющих методов используй wb_call"). Both the when and the when-not are explicit.

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