Yandex Metrika MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YANDEX_METRIKA_TOKEN | Yes | OAuth 2.0 Bearer token from Yandex 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 |
|---|---|
| list_countersA | List all Yandex.Metrica counters available to the authenticated user. Returns counter ID, name, site URL, and status. Supports search filtering. |
| get_counterA | Get full details of a single Yandex.Metrica counter by ID, including configuration, code snippet status, and goals count. |
| create_counterA | Create a new Yandex.Metrica counter for a website. Returns the new counter ID and tracking code. You need to install the tracking code on the site afterwards. |
| update_counterA | Update an existing Yandex.Metrica counter — change its name or site URL. |
| delete_counterA | Permanently delete a Yandex.Metrica counter. This action is irreversible — all historical data for this counter will be lost. |
| list_goalsA | List all goals configured for a Yandex.Metrica counter. Goals track conversions like page visits, button clicks, or multi-step funnels. |
| create_goalB | Create a new conversion goal for a counter. Supports types: 'url' (page visit), 'number' (page count threshold), 'step' (multi-step funnel), 'action' (JavaScript event). |
| delete_goalA | Delete a conversion goal from a counter. Historical goal data in reports is preserved. |
| export_logsA | Export raw visit or hit logs via the Logs API. Creates a log request and evaluates feasibility. Use source='visits' for session data, source='hits' for pageview data. |
| get_reportB | Flexible Yandex.Metrica reporting endpoint. Query any combination of metrics (ym:s:visits, ym:s:pageviews, ym:s:bounceRate, ym:s:avgVisitDurationSeconds, ym:s:users, ym:s:newUsers, etc.) with dimensions (ym:s:trafficSource, ym:s:searchEngine, ym:s:country, ym:s:browser, ym:s:deviceCategory, ym:s:date, etc.) over a date range. Supports filters and sorting. |
| get_report_comparisonA | Compare metrics between two date periods (A vs B). Useful for week-over-week, month-over-month, or campaign before/after analysis. |
| get_report_drilldownA | Drill down into report data hierarchically. Start at top level, then pass parent_id to explore sub-dimensions (e.g., country -> city, traffic source -> campaign). |
| get_traffic_summaryA | Quick traffic overview for a counter over a date range. Returns visits, pageviews, unique users, bounce rate, and average visit duration in one call. |
| get_traffic_sourcesB | Traffic sources breakdown — visits and users by source channel (organic search, direct, social, referral, ad). Quick way to see where traffic comes from. |
| get_top_pagesA | Top pages by pageviews for a counter. Returns URL, visits, pageviews, bounce rate, and avg duration for each page. Useful for content performance analysis. |
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 15 tools
Counter and goal tools are clearly separated by resource and action, and the specialized reporting tools have distinct intents. However, get_report is a flexible catch-all that overlaps with get_traffic_summary, get_traffic_sources, get_top_pages, get_report_comparison, and get_report_drilldown, which could cause misselection.
Tool names consistently follow a verb_noun pattern: list_/create_/update_/delete_ for resource collections, and get_ for single entities or report views. The naming makes both resource type and action predictable across the whole toolset.
15 tools is at the upper end of the ideal range, but the count is justified by the breadth of Yandex Metrika functionality: counter CRUD, goal management, log export, and multiple reporting variations. The reporting shortcuts add some redundancy but still map to concrete user needs.
Counter lifecycle is fully covered with create/read/update/delete, and reporting has broad query options with comparison, drilldown, and traffic summaries. The main gap is the missing update_goal operation, and export_logs only initiates/evaluates a log request without covering the full retrieval flow.