PR-CY MCP

get_metrika_page_depth_analysis

Получить количество сессий, где пользователи просмотрели больше указанного количества страниц из Яндекс.Метрики. Если даты не указаны, возвращаются данные за последние 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_page_depth_analysis"
  }
}

Input Schema

Name	Required	Description
`date_to`	No	Дата окончания периода в формате YYYY-MM-DD или значения: today, yesterday, ndaysAgo.
`date_from`	No	Дата начала периода в формате YYYY-MM-DD или значения: today, yesterday, ndaysAgo.
`min_pages`	No	Минимальное количество просмотренных страниц
`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.7/5.0

Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses the default 7-day window and that the page threshold is a 'more than' comparison, but says nothing about permissions, aggregation granularity, or result shape beyond what the output schema presumably covers.

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?

Two tight sentences, no filler, with the core purpose front-loaded and the default-behavior caveat second. Every clause earns its place.

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?

An output schema exists, so return values need no explanation, and the default-window rule is the main behavioral fact an agent needs. The remaining gap is the absence of any routing hint among the crowded get_metrika_* family, which for a read-only analytics tool is a minor but real shortfall.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it clarifies that dates being absent yields a 7-day default and that min_pages is a strict 'greater than' threshold (the schema wording 'minimum pages' alone is ambiguous between >= and >). That is genuine value beyond 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 names a specific verb+resource: counting sessions where users viewed more than a given number of pages, sourced from Yandex.Metrika. That is unambiguous on its own, but it never differentiates itself from the many sibling get_metrika_* analytics tools (e.g. get_metrika_pages_report, get_metrika_visits), so an agent must infer which metric tool applies.

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?

It states the default-window behavior (last 7 days when dates are omitted), which is a useful calling guideline, but it gives no when-to-use/when-not-to-use guidance and does not point to any alternative metric tool. Usage is implied by the tool name rather than explained.

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?