ya-metrics-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENABLED_TOOLS | No | Comma-separated list of allowed tools | |
| READ_ONLY_MODE | No | Restrict to read-only tools | false |
| YANDEX_API_KEY | Yes | Yandex OAuth token | |
| YANDEX_RETRIES | No | Retry attempts for 5xx errors | 3 |
| YANDEX_TIMEOUT | No | Request timeout in seconds | 30 |
| YANDEX_RETRY_DELAY | No | Base delay between retries (seconds) | 1.0 |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_countersA | List all Yandex Metrika counters available to this account. Use this to find counter IDs. |
| list_goalsA | List all conversion goals configured for a counter. Use goal IDs with get_goals_conversion. |
| get_account_infoB | Get basic account and counter information from Yandex Metrika. |
| get_visitsB | Retrieve visit statistics with optional date range (defaults to last 7 days). |
| sources_summaryC | Get comprehensive traffic sources overview and summary report. |
| sources_search_phrasesB | Retrieve search phrases and browser information from traffic sources. |
| get_traffic_sources_typesB | Analyze different types of traffic sources (organic, direct, referral). |
| get_search_engines_dataB | Get sessions and users data from search engines with optional filters. |
| get_new_users_by_sourceC | Identify which traffic sources are most effective in acquiring new users. |
| get_content_analytics_sourcesB | Get sources that drive users to website articles. |
| get_content_analytics_categoriesC | Retrieve overall statistics by content category. |
| get_content_analytics_authorsC | Get statistics on article authors performance. |
| get_content_analytics_topicsC | Analyze performance by article topics. |
| get_content_analytics_articlesC | Get detailed report on article views grouped by article. |
| get_user_demographicsB | Access user demographics and engagement by device category. |
| get_device_analysisC | Analyze user behavior by browser and operating system. |
| get_mobile_vs_desktopC | Compare traffic and engagement metrics between mobile and desktop users. |
| get_page_depth_analysisC | Get sessions where users viewed more than the specified number of pages. |
| get_regional_dataC | Get sessions and users data for specific regions/cities. |
| get_geographical_organic_trafficB | Analyze geographical distribution of organic traffic. |
| get_page_performanceC | Get page performance and bounce rate by URL path. |
| get_goals_conversionC | Track conversion rates for specified goals. |
| get_organic_search_performanceC | Analyze organic search performance by search engine and query. |
| get_conversion_rate_by_source_and_landingB | Get conversion rate analysis by traffic source and landing page. |
| get_ecommerce_performanceB | Get e-commerce performance by product category and region. |
| get_data_by_timeC | Get data for specific time periods grouped by day/week/month/quarter/year. |
| get_yandex_direct_experimentC | Get bounce rate for specific Yandex Direct A/B experiments. |
| get_browsers_reportB | Get browsers report without accounting for browser version. |
| get_drilldownB | Generate a single branch of a hierarchical tree-view report (drill-down). |
| compare_segmentsB | Compare two user segments side by side in a table report. |
| compare_segments_drilldownC | Compare two segments in a hierarchical tree-view report with drill-down capability. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mrkhachaturov/ya-metrics-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server