Yandex Webmaster MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YANDEX_WEBMASTER_TOKEN | Yes | OAuth-токен Яндекс.Вебмастер |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_hostsA | List all sites in Yandex.Webmaster: URL, verification status. |
| get_user_infoA | Get your Yandex Webmaster account info (user_id). |
| get_popular_search_queriesA | Per-query analytics: query text, shows, clicks, average position. The data behind 'which queries bring traffic'. |
| get_query_analyticsA | Aggregate search-traffic time series (total shows/clicks/position over a date range) — NOT per-query. |
| get_search_queriesA | [DEPRECATED — use get_popular_search_queries] Per-query search analytics: clicks, impressions, position. |
| get_indexingB | Indexing status summary for a host (quality index, problem counts). |
| get_indexing_historyA | Indexed / excluded page-count trend over time (detect deindexing). |
| submit_urlA | Submit a URL for re-crawling / re-indexing by Yandex (consumes daily quota). |
| get_recrawl_quotaB | Remaining daily re-crawl (re-indexing) quota for a host. |
| get_recrawl_taskA | Status of a re-crawl task by id (from submit_url). |
| get_sitemapsA | List sitemaps for a host: URL, status, last checked, indexed count. |
| get_diagnosticsA | Site diagnostics: crawl errors, DNS issues, server problems. |
| get_important_urlsB | Monitored important URLs for a host and their status history. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Most tools have distinct purposes (e.g., get_hosts lists sites, get_query_analytics aggregates time series), but get_popular_search_queries and get_search_queries overlap, with one explicitly deprecated. The descriptions clarify the distinction, so misselection is unlikely.
All tools follow a consistent 'get_' prefix with descriptive nouns, except submit_url which is a clear action verb. The pattern is uniform and readable, with no mixed conventions.
13 tools is a well-scoped size for a Yandex Webmaster server, covering diagnostics, analytics, indexing, and recrawl without being overwhelming or too sparse.
The surface covers core domain needs: diagnostics, analytics, indexing, sitemaps, and recrawl submission. Minor gaps exist (e.g., no verification or sitemap submission), but most workflows are supported. The deprecated get_search_queries slightly clutters the set.