Skip to main content
Glama
yandex-wordstat-mcp

yandex-wordstat-mcp

dynamics

Read-only

Retrieve how search volume for a phrase changes over time, with monthly, weekly, or daily aggregation and optional device and region filters for Yandex Wordstat trend analysis.

Instructions

How search volume for a phrase changes over time. share_percent is the phrase's share of all Yandex queries in that period. Dates are snapped automatically: weeks to Monday–Sunday, months to the 1st and the last day. Data lags by about a month; daily data covers only the last 60 days.

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": "dynamics"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoAggregation step.monthly
phraseYesSearch phrase, Wordstat operators allowed.
devicesNoDevice filter. Omit for all devices.
regionsNoRegion IDs or exact names, e.g. ["213"] or ["Москва"]. Omit for all regions.
to_dateNoEnd date (YYYY-MM-DD). Default: latest available.
from_dateNoStart date (YYYY-MM-DD). Default: ~12 months back for monthly, ~12 weeks for weekly, 55 days for daily. Daily data is only available for the last 60 days.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is known; the description then adds genuinely non-obvious behavior: automatic date snapping to week/month boundaries, an approximately one-month data lag, and the 60-day ceiling on daily data. It stops short of describing result shape or empty-period handling, but the added context is substantial.

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 purpose, then field semantics, then behavioral caveats — no filler. Minor inefficiency: the share_percent definition sits mid-paragraph rather than being grouped with the other output-related caveats.

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?

An output schema exists, so return-value documentation is not required, and the description covers the two things schema cannot: date snapping and data freshness/limits. What remains unstated is how periods with missing or zero data appear and whether the series includes absolute volume alongside share, both of which an agent might want to know.

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 description coverage is 100%, so the baseline is 3. The description earns above baseline by explaining that from_date/to_date are snapped to period boundaries (weeks to Monday–Sunday, months to the 1st and last day), which changes how an agent should reason about the date parameters and the returned buckets.

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?

Opens with a specific resource and behavior: "How search volume for a phrase changes over time," which tells an agent exactly what data comes back. It also defines the key output field share_percent. It does not distinguish itself from siblings like frequencies or top_requests, so an agent must infer the split from names alone.

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?

Usage is implied by the subject matter (time-series dynamics) rather than stated, and there is no explicit when-to-use/when-not or mention of an alternative tool. The data-lag and 60-day daily-window notes do implicitly constrain when this tool is the right choice, but only for the daily case.

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