io.github.dontsovcmc/yandex-metrika
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| METRIKA_TIMEOUT | No | Таймаут HTTP-запросов к API (секунды) | 30 |
| METRIKA_FILE_TIMEOUT | No | Таймаут скачивания файлов (секунды) | 60 |
| YANDEX_METRIKA_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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ym_searchA | Find available actions by intent. Optional domain filter: reporting, counters, goals, filters, grants, operations, segments, labels, accounts, delegates, annotations, access_filters, logs, uploads. Returns action ID, description, and JSON Schema of parameters. |
| ym_executeA | Execute action by ID. params_json validated against action schema. Use ym_search to discover actions and their schemas first. |
| ym_execute_fileA | Execute action that reads or writes a file (uploads/downloads). file_path must be under ~/... or /tmp/... Use ym_search to discover file actions (is_file=true). |
| ym_countersB | List counters. Optional filters: search_string, permission (own/view/edit), status (Active/Deleted), per_page, offset. |
| ym_counterC | Get counter details. field: goals,mirrors,grants,filters,operation. |
| ym_stat_dataB | Table report (GET /stat/v1/data). ids and metrics are comma-separated. Example: ids='12345', metrics='ym:s:visits,ym:s:users', dimensions='ym:s:browser', date1='7daysAgo', date2='today'. |
| ym_stat_data_bytimeC | Time-series report (GET /stat/v1/data/bytime). group: all/auto/minutes/hour/day/week/month/quarter/year. |
| ym_goalsB | List goals for a counter. |
| ym_segmentsB | List segments for a counter. |
| ym_grantsC | List access grants for a counter. |
| ym_log_requestsB | List log API requests for a counter. |
| ym_labelsA | List all labels. |
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 12 tools
Each tool has a clearly distinct purpose: search for actions, execute them, list specific resources (labels, counters, goals, etc.), and generate reports. There is no ambiguity between tools, and even similar report tools are differentiated by type.
All tools follow the 'ym_<resource_or_action>' pattern consistently. Names are descriptive and predictable, with only minor internal underscores (e.g., stat_data) which do not break the pattern.
12 tools is well-scoped for a Yandex Metrika server. It covers core resources (counters, goals, segments, etc.) and adds generic search/execute for extensibility without bloat.
The tool set covers all major Metrika operations with dedicated tools (counters, stats, goals, etc.) and provides a generic ym_execute for any remaining actions. This hybrid approach leaves no obvious gaps.