Skip to main content
Glama

Wildberries API: сырой запрос

wb_request
Destructive

Sends direct HTTP requests to allowed Wildberries API hosts for endpoints not yet in the catalog, accepting a URL or host/path with query and body parameters.

Instructions

Прямой HTTP-запрос к любому хосту *.wildberries.ru — на случай нового метода, которого ещё нет в каталоге. Разрешены только хосты wildberries.ru. Указывай url (или host+path), query, body.

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": {
      "method": "<method>"
    },
    "name": "wb_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoПолный URL (host и path), например https://common-api.wildberries.ru/ping
bodyNoТело запроса (JSON)
hostNoХост, если не указан url, например https://finance-api.wildberries.ru
pathNoПуть, если не указан url, например /api/v1/account/balance
queryNoQuery-параметры
methodYesHTTP метод
accountNoИмя аккаунта
headersNoДополнительные заголовки (Authorization игнорируется)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the arbitrary-write risk is known. The description adds a genuinely useful constraint not present in annotations — only *.wildberries.ru hosts are allowed — but says nothing about auth injection (the Authorization header is silently ignored per schema), rate limits, error behaviour, or what a destructive call actually does. Useful but thin for an unrestricted-method passthrough.

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?

Three short sentences, zero waste, with the escape-hatch purpose and the host restriction front-loaded before the parameter hint.

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

Completeness3/5

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

Eight parameters, a method enum, nested objects and no output schema — yet the description never mentions what a call returns, how errors surface, or how the account/token parameter interacts with the request. Adequate to call it, incomplete for a destructive raw-HTTP tool.

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 description coverage is 100%, so all 8 parameters are self-documenting. The description only restates the url vs host+path pairing and mentions query/body without adding precedence rules (e.g. what wins if both url and host+path are supplied) or any hints on method/account/headers. Baseline 3 applies.

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?

States a specific verb and resource ('Прямой HTTP-запрос к любому хосту *.wildberries.ru') plus its scope. The clause 'на случай нового метода, которого ещё нет в каталоге' explicitly positions it as the escape hatch against the catalog-driven siblings (wb_call, wb_get, wb_describe).

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

Usage Guidelines4/5

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

Gives a clear when-to-use condition: a new/unknown method not yet in the catalog. The inverse (use the catalog tools when the method exists) is strongly implied but never stated, and no sibling is named as the preferred alternative.

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