Skip to main content
Glama

Wildberries API: разделы и покрытие

wb_sections
Read-only

Lists Wildberries API sections with method counts, token status, and catalog build date, helping you see which sections are available before starting work.

Instructions

Обзор каталога: разделы 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_sections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and an output schema exists, so the description adds only modest extra context by hinting that token state and a catalog build date are included in the response. It does not discuss freshness of the build date or whether the catalog reflects the live API, which would be the genuinely non-obvious behavior here.

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?

Two sentences, no filler, with the payload contents front-loaded before the usage hint. Slightly denser than ideal because contents and recommendation are packed into a single run-on sentence, but nothing is wasted.

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 parameterless, read-only overview tool with an output schema and a readOnlyHint annotation, the definition covers purpose, payload contents, and timing well enough to invoke correctly. The only residual gap is any statement about how current the catalog build date is.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. Schema coverage is 100% and additionalProperties is false, leaving no ambiguity an agent could stumble on.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (WB API sections) and enumerates the concrete payload: method counts per section, token state, and catalog build date. It reads clearly as a catalog/overview tool distinct from the operational siblings (wb_call, wb_get, wb_request), though it never names a sibling to contrast with.

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 situational cue for when to reach for this tool (session start / orientation). It stops short of explicit exclusions or naming an alternative when you already know the section you need.

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