Skip to main content
Glama
yandex-wordstat-mcp

yandex-wordstat-mcp

frequencies

Read-only

Get base and exact 30-day search volumes for multiple phrases in one call to validate real demand and decide if each phrase merits its own page.

Instructions

Base and exact search volume over the last 30 days for a list of phrases in one call. Use it to check real demand for specific wordings instead of calling top_requests per phrase. base counts every query containing the words, so it is inflated by longer queries. exact counts only queries made of exactly these words in these forms ("!word1 !word2") — trust it when deciding whether a phrase deserves its own page. exact_share_percent is exact / base. Each phrase costs up to 2 API requests (1 with mode "exact" or "base"). A phrase that fails gets an error field; the others are still returned.

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": {
      "phrases": "<phrases>"
    },
    "name": "frequencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoboth = base and exact, or only one of them (half the API requests).both
devicesNoDevice filter. Omit for all devices.
phrasesYesPhrases to check, up to 7 words each.
regionsNoRegion IDs or exact names, e.g. ["213"] or ["Москва"]. Omit for all regions.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.7/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses request cost ('up to 2 API requests, 1 with mode exact or base') and partial-failure semantics ('a phrase that fails gets an error field; the others are still returned') — genuinely useful behavior not captured by annotations. It stops short of noting rate limits or result ordering, which keeps it from a 5.

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?

Six short sentences, front-loaded with the capability and the sibling alternative, then the metric semantics, then cost and failure behavior. Each sentence carries distinct decision-relevant information with no restated boilerplate.

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

Completeness5/5

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

For a four-parameter, fully annotated, output-schema-backed read tool, the description covers purpose, metric interpretation, cost, and error behavior. Nothing an agent needs to select or invoke it correctly appears to be missing.

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 is 3, but the description adds real semantic meaning: it explains how base is inflated by longer queries, how exact restricts to those exact word forms, and that exact_share_percent is exact/base. This is interpretive guidance the schema does not supply.

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 opening sentence states a specific verb (retrieve search volume), resource (phrases), scope (base and exact), time window (last 30 days), and a batching property (in one call). It also names the sibling top_requests, so an agent can distinguish batch frequency lookup from per-phrase request listing without opening a 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?

It explicitly routes the agent away from iterating top_requests per phrase, and gives a decision rule for which metric to trust ('trust exact when deciding whether a phrase deserves its own page'). The mode parameter's cost trade-off is also framed, leaving little to infer.

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