PR-CY MCP

get_metrika_pages_report

Получить отчёт по страницам и метрикам из Яндекс.Метрики. По умолчанию возвращает пользователей и визиты по начальным URL страниц. Если даты не указаны, возвращаются данные за последние 7 дней.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>"
    },
    "name": "get_metrika_pages_report"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Список метрик, по которым осуществляется сортировка.
`limit`	No	Количество результатов для возврата (максимум 100)
`date_to`	No	Дата окончания периода в формате YYYY-MM-DD или значения: today, yesterday, ndaysAgo.
`filters`	No	Фильтры в формате API Метрики (передавайте сырую строку)
`metrics`	No	Список метрик (максимум 20, например: ym:s:users, ym:s:visits, ym:s:pageviews, ym:s:bounceRate)
`goal_ids`	No	Список идентификаторов целей для получения метрик по достижениям целей и целевым посетителям
`date_from`	No	Дата начала периода в формате YYYY-MM-DD или значения: today, yesterday, ndaysAgo.
`dimensions`	No	Список измерений (максимум 10, например: ym:s:startURL, ym:s:URLPath)
`project_id`	Yes	Идентификатор проекта.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses default metrics, default dimension behavior, and the 7-day fallback when dates are omitted. It does not mention read-only safety, permissions, rate limits, or pagination, which are relevant for a reporting tool with nine parameters.

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 three concise sentences, front-loaded with the core purpose and followed by the most important defaults. There is no redundant or filler text.

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?

Given the rich input schema and the presence of an output schema, the description provides the key operational defaults: default metrics/dimension and the 7-day date fallback. However, it is incomplete for tool selection because it does not position this report relative to the many sibling Metrika reporting tools.

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 the schema already documents the parameters in detail. The description adds some meaning by explaining the default report output and the last-7-days behavior when dates are not supplied, but most parameter semantics remain anchored in the schema.

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 states a clear verb and resource: retrieve a report on pages and metrics from Yandex.Metrika. It also identifies the default output as users and visits by start URL. However, it does not explicitly distinguish this tool from sibling Metrika report tools such as get_metrika_visits or get_metrika_custom_query.

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

Usage Guidelines3/5

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

The default behavior (users and visits by start URL) implies that this tool is for page-level traffic reporting, but there is no explicit guidance on when to choose it over alternatives. It does not name sibling tools or state exclusions, leaving selection to inference.

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

All PR-CY MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?