Skip to main content
Glama
yandex-wordstat-mcp

yandex-wordstat-mcp

top_requests

Read-only

Retrieve 30-day search volume plus popular queries containing a phrase and associated queries for keyword research. Filter results by region and device.

Instructions

Search volume for a phrase over the last 30 days, plus the most popular queries containing it and similar ("associated") queries. Use for keyword research.

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": {
      "phrase": "<phrase>"
    },
    "name": "top_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
phraseYesSearch phrase, Wordstat operators allowed.
devicesNoDevice filter. Omit for all devices.
regionsNoRegion IDs or exact names, e.g. ["213"] or ["Москва"]. Omit for all regions.
num_phrasesNoHow many related queries to return.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds the fixed 30-day lookback window, which the schema does not state. It says nothing about result caps, rate limits, or what happens with Wordstat operators on large phrases, so it adds moderate value only.

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 tight sentences with the primary output (volume) front-loaded and the secondary outputs after it. The parenthetical gloss on "associated" is slightly clumsy but earns its place by clarifying jargon.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values need no explanation, and all four parameters are documented in the schema. The remaining gap is orientation within a family of keyword-research siblings, which the description does not address at all.

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 description coverage is 100%, including per-parameter notes on device filters, region formats, and the num_phrases range, so the schema carries the burden. The description adds no meaning beyond it, which is the baseline case for full coverage.

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: search volume for a phrase over a 30-day window, plus popular containing queries and associated queries. An agent knows exactly what data comes back. It stops short of differentiating from siblings like dynamics or frequencies, so it does not reach a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

"Use for keyword research" is the only usage cue and is essentially a restatement of the tool's category. There is no when-not guidance and no named alternative for the sibling tools that also operate on phrases (dynamics, frequencies, regions_distribution), so routing must be inferred.

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