Skip to main content
Glama
Yandex Metrica MCP

Yandex Metrica MCP

Список счётчиков Метрики

list_counters
Read-onlyIdempotent

Retrieves Yandex Metrica counters available to the token, with IDs, names, and site domains; filter by name or site to locate the correct counter for statistics or goals.

Instructions

Возвращает счётчики Яндекс Метрики, доступные токену (Management API). У каждого счётчика есть id, name и site2 (домен сайта) — id используется в get_statistics и list_goals. Фильтр по подстроке имени или сайта задаётся параметром search. На один сайт бывает несколько счётчиков (старый и новый, тестовый, отдельный для поддомена) — у каждого свои данные.

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": "list_counters"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNoСмещение для постраничной выдачи, отсчёт с 1.
searchNoПодстрока для фильтра счётчиков по имени или сайту, без учёта регистра.
perPageNoМаксимум счётчиков в ответе. По умолчанию 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.4.1
    • changedInput schema / properties / offset / description
      Previous value: -"1-based offset for pagination."New value: +"Смещение для постраничной выдачи, отсчёт с 1."
    • changedInput schema / properties / perPage / description
      Previous value: -"Max counters to return. Default 100."New value: +"Максимум счётчиков в ответе. По умолчанию 100."
    • changedInput schema / properties / search / description
      Previous value: -"Case-insensitive substring to filter counters by name or site."New value: +"Подстрока для фильтра счётчиков по имени или сайту, без учёта регистра."
  2. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so safety is covered. The description adds genuinely useful behavior: results are scoped to the token's permissions, and a single site may yield multiple counters (old/new, test, subdomain) each with separate data. It says nothing about pagination behavior, which the schema only partly implies.

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

Conciseness4/5

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

Front-loaded with the action and resource, then the returned fields, then cross-references and the search filter. Four short sentences, each carrying content; the final caveat about multiple counters per site is the only one that could be trimmed but it prevents real misinterpretation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by listing the returned fields (id, name, site2). Combined with annotations covering the read-only profile and the schema covering all three params, an agent has what it needs to call this correctly; only pagination semantics are left unstated.

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%, so offset/perPage/search are already fully documented, making the baseline 3. The description only restates that `search` filters by name or site substring and omits offset/perPage entirely, adding no syntax or format detail beyond the schema.

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?

States a specific verb and resource ('Возвращает счётчики Яндекс Метрики, доступные токену') plus the API it targets (Management API). It also names the fields returned (id, name, site2), so an agent knows exactly what it gets without opening the schema, and it is clearly distinct from get_statistics/list_goals.

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

Usage Guidelines4/5

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

Explicitly routes the agent: the id from this tool feeds get_statistics and list_goals, which is the key when-to-use context. It also explains the `search` filter's purpose. It stops short of stating exclusions or prerequisites (e.g. needing a valid token/login first), so it is clear context without full when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.