Skip to main content
Glama
Sign In
Yandex Wordstat MCP

Yandex Wordstat MCP

by tvermolaev-source
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Search Dynamics

dynamics

Get search volume dynamics for a keyword over daily, weekly, or monthly intervals. Understand trend changes to inform SEO and content planning.

Instructions

Returns search volume dynamics (trend) for a keyword over time. Daily granularity: last 59 days. Weekly: last 52 weeks. Monthly (default): last 12 months.

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
periodNoTime granularity (default: monthly)
phraseYesKeyword to analyze trends for
toDateNoEnd date YYYY-MM-DD (auto-aligned if omitted)
devicesNoFilter by device types
regionsNoArray of region IDs to scope the query
fromDateNoStart date YYYY-MM-DD (auto-aligned if omitted)

Output Schema

NameRequiredDescriptionDefault
trendYes
dynamicsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Despite no annotations, the description discloses the return type (trend), granularity options (daily/weekly/monthly), and explicit time windows (last 59 days, 52 weeks, 12 months). This provides adequate behavioral transparency for a simple read tool.

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?

The description is two sentences, front-loaded with the primary purpose, followed by granularity details. Every word earns its place; no redundancy or filler.

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?

The output schema documents return values, and parameters are fully described in the schema. The description adds context for time ranges and defaults. For a trend tool, this is complete enough; no gaps remain.

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% with parameter descriptions. The description adds value by explaining the default period (monthly) and the time ranges associated with each granularity, which are not in the schema. This extra context enhances parameter understanding.

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 description clearly states the tool returns 'search volume dynamics (trend) for a keyword over time.' It specifies the exact resource (keyword) and output type (trend). Siblings focus on regions and top requests, so this tool is well-distinguished.

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?

The description implies usage by mentioning granularity options and their time ranges, but it does not explicitly state when to use this tool versus alternatives or provide any exclusions. Usage context is clear but lacks direct guidance.

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

Deploy Server

Other Tools