Skip to main content
Glama

WB Root Info (imt_id)

wb_root_info
Read-onlyIdempotent

Fetch a Wildberries SKU's basket CDN card metadata and return its imt_id (root ID) to group product variants for review queries.

Instructions

Fetch full card metadata from basket CDN. Returns imt_id (root_id) for review pool.

All variants of one product share imt_id. Reviews indexed by imt_id, NOT by nmId.

Full field list and error codes: guide://wb/wb_root_info.

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": {
      "nm_id": "<nm_id>"
    },
    "name": "wb_root_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
nm_idYesnmId (positive integer). The SKU whose basket CDN card.json is fetched for imt_id resolution.

Output Schema

NameRequiredDescriptionDefault
metaNo
colorsNo
imt_idNo
optionsNo
host_usedNo
subj_nameNo
compositionsNo
subj_root_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond that — the basket CDN source and the data-model rule that all product variants share one imt_id — but says nothing about auth needs, rate limits, or failure behavior except by pointing at `guide://wb/wb_root_info`.

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 short sentences, front-loaded with the verb and resource, then the output, then the data-model caveat, then a pointer to extended docs. No filler, though the telegraphic style is slightly clipped.

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 single-parameter read tool with a full output schema and rich annotations, an agent has what it needs: purpose, output identity, the imt_id sharing rule, and a doc pointer for fields and error codes. Only the alternative-tool routing is absent.

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?

With one parameter and 100% schema coverage, the schema already defines nm_id as the positive-integer SKU whose card.json is fetched for imt_id resolution. The description's 'reviews indexed by imt_id, NOT by nmId' reinforces the input-to-output mapping but does not add syntax or constraint detail beyond what the schema states.

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 verb and resource ('Fetch full card metadata from basket CDN') and immediately names the output it exists to produce: 'Returns imt_id (root_id) for review pool.' That imt_id-resolution framing distinguishes it from a generic card fetch like wb_card, though the description never names the sibling it is not.

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 clear context for when this tool is the right call: you need imt_id because 'Reviews indexed by imt_id, NOT by nmId.' That is an actionable selection rule. It stops short of explicit alternatives or exclusions (e.g., 'use wb_card if you only need price/stock'), so it is not a 5.

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