Skip to main content
Glama

Wildberries API: поиск метода

wb_search
Read-only

Search Wildberries Seller API methods by keywords or path fragments and return method IDs, paths, read-only status, and brief descriptions to guide schema lookup or API calls.

Instructions

Найти метод Wildberries Seller API по словам (например "остатки", "отзывы", "поставки", "цены"). Начни с этого инструмента. Возвращает id, метод, путь, признак readonly и краткое описание. Дальше: wb_describe для схемы, 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": {
      "query": "<query>"
    },
    "name": "wb_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoall — всё, read — только чтение, write — только изменяющие методы
limitNoСколько результатов вернуть (по умолчанию 10)
queryYesПоисковый запрос: русские или английские слова, часть operationId или пути
sectionNoОграничить разделом: например 02-items, 11-analytics, 13-finances

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

The readOnlyHint=true annotation is consistent with a keyword search, and the description reinforces it by promising a readonly flag in the results. It adds useful behavioral context beyond the annotations (the returned fields and the follow-up workflow) but says nothing about ranking, empty result sets, or how limits interact with the output, so it stops short of full disclosure.

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, front-loaded with purpose and examples, then the return fields, then the next-step routing. Every sentence carries information an agent needs, and no wording is repeated from the title or schema.

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?

With a readOnlyHint annotation, full schema coverage, and an output schema, the description only needs to cover purpose and workflow, which it does. The minor gap is guidance on result behavior (ranking, what an empty match looks like), which is not strictly required given the output schema.

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 meaning by illustrating the kinds of query words that work ("остатки", "отзывы", "поставки", "цены"). The mode, limit, and section parameters are left entirely to their already complete schema descriptions, which is acceptable at this coverage level.

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 (find a Wildberries Seller API method by keywords) and gives concrete example queries such as "остатки" and "отзывы". It also lists the fields returned (id, method, path, readonly flag, short description), so an agent can distinguish it from wb_call, wb_describe, and the other siblings without opening any 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?

The definition explicitly tells the agent to start with this tool and then hands off to named alternatives: wb_describe for a schema and wb_call for invocation. That is an explicit when-to-use plus a routing chain to the siblings, leaving nothing to inference.

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