Skip to main content
Glama
Sign In
yandex-metrica-mcp

yandex-metrica-mcp

by BoxLab-Ltd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Describe Metrica counter

describe_counter
Read-only

Reads a Yandex Metrica counter's configuration sections, including goals, so you can get the goal IDs needed before building conversion metrics.

Instructions

Read a single counter's configuration — settings, goals, segments, filters, operations and access grants and chart annotations — choosing sections with include. The goals section returns the goal ids needed to build conversion metrics (ym:s:goalreaches / conversionRate) in run_report, so call this with include=["goals"] before any conversion question. To list the account's counters, use get_metadata. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "describe_counter"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeNoWhich configuration sections to return. Default ["settings","goals"]. "goals" gives the goal ids needed for conversion metrics in run_report; "grants" is a read-only access audit; "annotations" lists the notes pinned to chart dates (releases, campaigns, outages) — useful context when explaining a change.
counterIdNoYandex Metrica counter id. Optional if YANDEX_METRIKA_COUNTER_ID is configured.
fullResponseNoIf true, return the full raw objects with every field. Default false: a curated subset to save context.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.1
    • changedInput schema / properties / include / description
      Previous value: -"Which configuration sections to return. Default [\"settings\",\"goals\"]. \"goals\" gives the goal ids needed for conversion metrics in run_report; \"grants\" is a read-only access audit."New value: +"Which configuration sections to return. Default [\"settings\",\"goals\"]. \"goals\" gives the goal ids needed for conversion metrics in run_report; \"grants\" is a read-only access audit; \"annotations\" lists the notes pinned to chart dates (releases, campaigns, outages) — useful context when explaining a change."
    • changedInput schema / properties / include / items / enum
      Previous value: -[
-  "settings",
-  "goals",
-  "segments",
-  "filters",
-  "operations",
-  "grants"
-]New value: +[
+  "settings",
+  "goals",
+  "segments",
+  "filters",
+  "operations",
+  "grants",
+  "annotations"
+]
  2. First observedv0.3.0

TDQS

A4.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, and the description mostly restates that with 'Read-only.' It adds some useful return context, notably that the goals section supplies goal ids for run_report, but does not cover auth needs, rate limits, or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and dense: it states the resource, section selection, conversion use case, alternative sibling tool, and read-only nature without filler. The section list is long but directly useful for understanding what can be returned.

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?

For a read-only single-counter configuration tool with complete parameter schema coverage and safety annotations, the description covers purpose, usage routing, key return semantics, and the relevant sibling alternative. No output schema exists, but the essential return behavior for conversion metrics is explained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the schema already documents the include enum, counterId, and fullResponse behavior. The description echoes the include=goals use case but adds little meaning beyond the schema for the other parameters.

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?

The description states a specific verb and resource: reading a single counter's configuration, with named sections. It also distinguishes the tool from get_metadata (listing counters) and run_report (conversion metrics).

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

Usage Guidelines5/5

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

It gives explicit routing: use include=["goals"] before any conversion question, and use get_metadata to list the account's counters. The alternatives and triggering conditions are named directly.

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