Retrieve Yandex Wordstat regional demand for a phrase over the last 30 days to identify where search interest is highest and guide ad targeting.
Get Wordstat demand by region for the last 30 days through the server budget gate.
| Name | Required | Description | Default |
|---|---|---|---|
| phrase | Yes | ||
| region | No | REGION_ALL | |
| devices | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden of behavioral disclosure. It mentions 'through the server budget gate,' hinting at some budget-controlled execution, but does not explain what that means, whether the operation is read-only, what limits apply, or what side effects may occur.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler. It efficiently communicates the core action even though it omits important operational details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations and only a one-sentence description, the agent lacks critical context: what 'server budget gate' means, how region values are specified, how devices affect results, and how this tool relates to sibling Wordstat tools. The output schema exists but does not compensate for missing invocation context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not compensate. Parameters like phrase, region, and devices are only named; their accepted values, formats, and semantics are unexplained. The phrase 'by region' gives a weak hint about the region parameter but nothing more.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action and scope: 'Get Wordstat demand by region' with a 30-day window. This makes it distinguishable from related tools like yandex_wordstat_get_top and yandex_wordstat_dynamics, though it does not explicitly differentiate itself from yandex_wordstat_regions_tree.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives such as yandex_wordstat_get_top, yandex_wordstat_dynamics, or yandex_wordstat_regions_tree. The regional focus implies the use case, but there is no explicit when/when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.