Skip to main content
Glama

Wildberries API: обновить каталог

wb_refresh

Download fresh Wildberries OpenAPI specs and rebuild the method catalog when the API changes, optionally from local YAML files.

Instructions

Скачать свежие OpenAPI-спеки с dev.wildberries.ru и пересобрать каталог методов (когда WB меняет API). Требует сеть; занимает несколько секунд.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
langNoЯзык описаний (по умолчанию ru)
fromDirNoСобрать из локальной папки со .yaml вместо скачивания

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false; the description adds value beyond them by disclosing the network requirement and the several-second duration, plus the fact that the catalog is rebuilt rather than merely read. It stops short of saying whether the existing catalog is replaced or merged and what happens on a failed download, but the operational profile is largely covered.

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?

Two short sentences, zero filler. The action is front-loaded, followed by the trigger condition, the prerequisite and the expected latency — every clause earns its place.

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 two-parameter, zero-required maintenance tool with annotations but no output schema, the description covers purpose, trigger, prerequisite and cost. The only omission is where the rebuilt catalog lands or what the caller gets back, which is minor given the annotations carry the safety profile.

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% with descriptions and an enum on lang, so the schema already documents both parameters. The description doesn't mention the fromDir option at all, and its 'download from the site' framing actually points away from that local-folder mode, so it adds no meaning beyond the schema — baseline 3.

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 — download fresh OpenAPI specs from dev.wildberries.ru and rebuild the method catalog — which is clearly distinct from the runtime-call siblings (wb_call, wb_get, wb_request). An agent can tell this is a maintenance/refresh tool 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 Guidelines4/5

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

The parenthetical '(когда WB меняет API)' gives an explicit trigger condition for when to run it, and 'Требует сеть' signals a prerequisite. It does not name alternatives or say when not to use it, but the sibling category (runtime API calls) is different enough that this is a minor gap.

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