Skip to main content
Glama
artgas1

yandex-metrika-mcp-server

by artgas1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Список доступных счетчиков

metrika_counter_list
Read-onlyIdempotent

List Yandex Metrica counters accessible to the user, with optional filters for status, type, and search.

Instructions

Список доступных счетчиков. Возвращает список существующих счетчиков, доступных пользователю. [GET https://api-metrika.yandex.net/management/v1/counters] Документация: https://yandex.ru/dev/metrika/ru/management/openapi/counter/counters.md

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoСортировка: По умолчанию: Default.
typeNoФильтр по типу счетчика.
fieldNoОдин или несколько дополнительных параметров возвращаемого объекта. Названия дополнительных параметров указываются в любом порядке через запятую, без пробелов. Например: `field=goals,mirrors,grants,filters,operations,counter_flags,measurement_tokens`.
offsetNoПорядковый номер счетчика, с которого начнется выдача списка счетчиков. Первый счетчик имеет номер 1. Максимальный номер — 100 000, поскольку пользователь не может иметь более 100 000 счётчиков. По умолчанию: 1.
robotsNoУчитывать ли роботов. По умолчанию: true.
statusNoФильтр по статусу счетчика. По умолчанию включен. По умолчанию: Active.
reverseNoВыдать счетчики в обратном или прямом порядке сортировки. По умолчанию: true.
callbackNoФункция обратного вызова, которая обрабатывает ответ API.
favoriteNoФильтр по счетчикам, которые были добавлены в **Избранные**. По умолчанию: false.
label_idNoФильтр по метке.
per_pageNoКоличество счетчиков, которые вы хотите получить. Максимум за один запрос — 10 000 счётчиков. По умолчанию: 1000.
permissionNoФильтр по уровню доступа к счетчику. Параметр может содержать несколько значений, разделенных запятой:
counter_idsNoСписок идентификаторов счетчиков, которые вы хотите получить.
search_stringNoФильтр по строке. Можно указать:

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.3.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the description does not need to establish that this is a safe read operation. It adds the concrete GET endpoint and a documentation link, plus the 'available to the user' scoping, which is context beyond annotations, but it does not describe pagination behavior or response shape.

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

Conciseness3/5

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

The description is brief and includes useful endpoint and documentation links, but the opening phrase 'Список доступных счетчиков' redundantly repeats the title before the next sentence restates it. It is efficient overall, but not every phrase earns its place.

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

Completeness3/5

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

The schema documents the parameters thoroughly and annotations signal a safe read-only operation, so the description is adequate for a simple list call. However, there is no output schema inherited, and the description does not explain the response envelope, pagination, or metadata beyond saying it returns a list of counters.

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 all 14 parameters are already documented in the input schema. The description adds no additional parameter-level meaning, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Возвращает список существующих счетчиков') and scopes it to counters available to the user. It is easy to distinguish from the sibling metrika_counter_get by the 'list' semantics, though the description does not explicitly call out that distinction.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as metrika_counter_get or the metrika_stat_* reporting tools. The intended use is only implied by the word 'list', and no exclusions or alternative routing are provided.

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