Skip to main content
Glama
Yandex Wordstat MCP

Yandex Wordstat MCP

Динамика спроса во времени

dynamics
Read-onlyIdempotent

Track how search demand for a phrase changes over time, returning dates, counts, and share of total Yandex searches to assess seasonality and trends.

Instructions

Возвращает, как менялся спрос на фразу во времени, — ряд {date, count, share}, где share — доля от всех поисковых запросов Яндекса. Подходит для оценки сезонности и тренда. period задаёт шаг ряда (daily/weekly/monthly); period и fromDate обязательны, значений по умолчанию у API нет. fromDate/toDate — метки времени RFC3339. Границы диапазона API сверяет по UTC и требует выравнивать по шагу: monthly — fromDate первое число месяца, toDate последний день месяца; weekly — fromDate понедельник, toDate воскресенье; daily — любые дни, но fromDate не старше 60 дней. Без toDate ряд идёт до последних доступных данных.

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>",
      "period": "<period>",
      "fromDate": "<fromDate>"
    },
    "name": "dynamics"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodYesШаг ряда: daily, weekly или monthly. От него зависит, какими должны быть fromDate и toDate.
phraseYesПоисковая фраза для анализа.
toDateNoКонец диапазона (RFC3339, дата сверяется по UTC), например 2026-03-31T00:00:00Z. Для monthly — последний день месяца, для weekly — воскресенье, для daily — любой день. Без параметра — до последних доступных данных.
devicesNoФильтр по устройствам: любые из all, desktop, phone, tablet. Без параметра — все устройства.
fromDateYesНачало диапазона (RFC3339, дата сверяется по UTC), например 2026-01-01T00:00:00Z. Для monthly — первое число месяца, для weekly — понедельник, для daily — не старше 60 дней.
regionIdsNoId регионов, которыми ограничить спрос, например [213] (Москва), [2] (Санкт-Петербург). Id берутся из list_regions. Без параметра — все регионы.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.5.0
    • changedInput schema / properties / fromDate / description
      Previous value: -"Начало диапазона (RFC3339), например 2026-01-01T00:00:00Z."New value: +"Начало диапазона (RFC3339, дата сверяется по UTC), например 2026-01-01T00:00:00Z. Для monthly — первое число месяца, для weekly — понедельник, для daily — не старше 60 дней."
    • changedInput schema / properties / period / description
      Previous value: -"Шаг ряда. По умолчанию monthly."New value: +"Шаг ряда: daily, weekly или monthly. От него зависит, какими должны быть fromDate и toDate."
    • changedInput schema / properties / toDate / description
      Previous value: -"Конец диапазона (RFC3339), выровненный по границе периода."New value: +"Конец диапазона (RFC3339, дата сверяется по UTC), например 2026-03-31T00:00:00Z. Для monthly — последний день месяца, для weekly — воскресенье, для daily — любой день. Без параметра — до последних доступных данных."
    • changedInput schema / required
      Previous value: -[
      -  "phrase"
      -]New value: +[
      +  "phrase",
      +  "period",
      +  "fromDate"
      +]
  2. Changed6 schema fields changedv2.4.0
    • changedInput schema / properties / devices / description
      Previous value: -"Device filter: any of all, desktop, phone, tablet. Omit for all devices."New value: +"Фильтр по устройствам: любые из all, desktop, phone, tablet. Без параметра — все устройства."
    • changedInput schema / properties / fromDate / description
      Previous value: -"Range start (RFC3339), e.g. 2026-01-01T00:00:00Z."New value: +"Начало диапазона (RFC3339), например 2026-01-01T00:00:00Z."
    • changedInput schema / properties / period / description
      Previous value: -"Granularity of the series. Default monthly."New value: +"Шаг ряда. По умолчанию monthly."
    • changedInput schema / properties / phrase / description
      Previous value: -"The search phrase to research."New value: +"Поисковая фраза для анализа."
    • changedInput schema / properties / regionIds / description
      Previous value: -"Region ids to scope demand to, e.g. [213] (Moscow), [2] (St. Petersburg). Get ids from list_regions. Omit for all regions."New value: +"Id регионов, которыми ограничить спрос, например [213] (Москва), [2] (Санкт-Петербург). Id берутся из list_regions. Без параметра — все регионы."
    • changedInput schema / properties / toDate / description
      Previous value: -"Range end (RFC3339), aligned to the period boundary."New value: +"Конец диапазона (RFC3339), выровненный по границе периода."
  3. Changed3 schema fields changedv2.0.1
    • addedInput schema / properties / fromDate / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(\\.\\d+)?(Z|[+-]\\d{2}:\\d{2})$"
    • changedInput schema / properties / regionIds / items / anyOf
      Previous value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "string"
      -  }
      -]New value: +[
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "pattern": "^\\d+$",
      +    "type": "string"
      +  }
      +]
    • addedInput schema / properties / toDate / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(\\.\\d+)?(Z|[+-]\\d{2}:\\d{2})$"
  4. Changed2 schema fields changedv2.0.0
    • changedInput schema / properties / fromDate / description
      Previous value: -"Range start. cloud: RFC3339; oauth: YYYY-MM-DD."New value: +"Range start (RFC3339), e.g. 2026-01-01T00:00:00Z."
    • changedInput schema / properties / toDate / description
      Previous value: -"Range end (aligned to the period). cloud: RFC3339; oauth: YYYY-MM-DD."New value: +"Range end (RFC3339), aligned to the period boundary."
  5. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the description is free to add what annotations cannot: the API validates boundaries in UTC, requires range alignment to the step (monthly = first/last day, weekly = Monday/Sunday), caps daily ranges at 60 days back, and extends to the latest available data when toDate is omitted. These are real behavioral constraints an agent must satisfy before calling.

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?

Front-loaded with the return shape and share definition, then use case, then constraints — a sound order with no filler. The per-period alignment rules partially duplicate the schema's parameter descriptions, costing some tightness.

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?

With no output schema, the description carries the return contract and does so precisely ({date, count, share} plus share semantics), and it covers required params, defaults, UTC validation and boundary alignment. Everything an agent needs to form a valid call is present; devices/regionIds are fully documented in the schema.

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; the description goes slightly beyond by noting that period and fromDate are required and that the API supplies no defaults, which the schema's required list does not convey explicitly. It restates the alignment rules already present in the fromDate/toDate descriptions and says nothing about devices or regionIds, which rely entirely on the schema.

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?

States a specific verb and resource ('возвращает, как менялся спрос на фразу во времени') and immediately specifies the returned series shape {date, count, share} with the meaning of share defined. This clearly separates it from ranking-style siblings like top_requests or region listing tools, and lets an agent decide without opening the schema.

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

Usage Guidelines4/5

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

'Подходит для оценки сезонности и тренда' gives a concrete use case, and the note that period and fromDate are mandatory with no API defaults prevents a common failure. It does not name an alternative tool or state when not to use it (e.g. single-point volumes vs time series), so it stops short of full routing 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