Skip to main content
Glama

Wildberries API: вызов метода

wb_call
Destructive

Call changing Wildberries API methods by ID to create, update, or delete prices, product cards, orders, supplies, ads, and review replies; warns about consequences before applying changes.

Instructions

Вызвать ИЗМЕНЯЮЩИЙ метод Wildberries API по id (создание/обновление/удаление: цены, карточки, заказы, поставки, реклама, ответы на отзывы). Перед вызовом предупреди пользователя о последствиях. Для чтения используй wb_get — он не требует подтверждения. Параметры path/query/header передавай в "params" по их именам из wb_describe, JSON-тело — в "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": {
      "id": "<id>"
    },
    "name": "wb_call"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is known. The description adds a confirmation protocol ('Перед вызовом предупреди пользователя о последствиях') and ties the warning requirement to the read-only sibling, which is genuine behavioral context. It stops short of describing return values, partial failure, or irreversibility on error.

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

Conciseness4/5

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

Four sentences, zero filler, with the destructive purpose front-loaded ahead of the confirmation rule and the parameter-routing instructions. The long parenthetical enumeration of resource categories is mildly redundant against 'ИЗМЕНЯЮЩИЙ' but still helps an agent match intent.

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 generic dispatcher across many endpoints this is well scoped: it covers purpose, the read/write fork, what to ask the user, and how to map arguments. With no output schema, an agent still lacks guidance on response shape and error handling, which keeps it below 5.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds real routing semantics absent from the schema: path/query/header values must be placed in 'params' under names discovered in wb_describe, a JSON payload goes in 'body', and 'id' comes from wb_search. That is meaningfully more than the property-level descriptions provide.

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 states a specific verb and resource ('Вызвать ИЗМЕНЯЮЩИЙ метод Wildberries API по id') and immediately enumerates the mutation categories (prices, cards, orders, supplies, ads, review replies). It explicitly contrasts with the sibling wb_get, so an agent can distinguish the two without opening either 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 both when to use this tool (idempotent-mutating operations by method id) and when not to (reads should go to wb_get, which needs no confirmation). It also prescribes a prerequisite behavior — warn the user before calling — and tells the agent to resolve parameter names via wb_describe and the id via wb_search.

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