PR-CY MCP

get_metrika_sources_summary

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

Input Schema

Name	Required	Description
`sort`	No	Список метрик, по которым осуществляется сортировка.
`limit`	No	Количество результатов для возврата (максимум 100)
`date_to`	No	Дата окончания периода в формате YYYY-MM-DD или значения: today, yesterday, ndaysAgo.
`date_from`	No	Дата начала периода в формате YYYY-MM-DD или значения: today, yesterday, ndaysAgo.
`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.6/5.0

Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It does disclose one real behavioral trait: the default 7-day window when dates are omitted, which the schema does not explain. However, it says nothing about permissions/auth needs, rate limits, or whether results are paginated or aggregated.

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 short sentences, with the core purpose front-loaded and the default-window caveat immediately after. No filler or repetition.

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?

An output schema exists, so return values need not be explained, and all five parameters are documented in the schema. Still, the description does not clarify what 'источники трафика' means here (channels, referrers, UTM groupings) or how sort/limit affect the result, leaving the agent to infer the report's shape.

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 description coverage is 100%, so the baseline is 3. The description earns one step above that by explaining what a null/missing date range means (last 7 days), which resolves an ambiguity left open by the schema's 'default: null' on date_from/date_to.

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 specific verb and resource: 'Получить сводку по источникам трафика из Яндекс.Метрики'. It is clearly a read/aggregate operation, but it does not distinguish itself from the many sibling Metrika reports (get_metrika_visits, get_metrika_search_engines_data, get_metrika_geographical_organic_traffic).

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 usage context is only implied: the tool is for traffic-source summaries, and omitting dates yields a 7-day window. There is no explicit guidance on when to choose it over the other Metrika summary tools, and no exclusions or prerequisites are stated.

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?