PR-CY MCP

get_metrika_goals_conversion

Получить количество пользователей и коэффициенты конверсии для указанных целей из Яндекс.Метрики. Если даты не указаны, возвращаются данные за последние 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>",
      "goal_ids": "<goal_ids>"
    },
    "name": "get_metrika_goals_conversion"
  }
}

Input Schema

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

B3.3/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 that data for the last 7 days is returned when dates are omitted, but it does not state that this is a read-only operation, mention permission requirements, rate limits, or data freshness beyond that default.

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 sentences, both front-loaded and free of repetition or filler. The purpose is stated first, followed by the default date behavior, with no wasted words.

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 and parameter descriptions are complete, so return values and argument details need not be explained. However, given no annotations, the description could do more to explain how goal_ids are obtained and how this differs from related Metrika reporting tools, leaving an agent with only adequate context.

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 all parameters including date formats and allowed relative values. The description adds no parameter meaning beyond the implicit default date range, which is not tied to a specific parameter in the text.

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: retrieve user counts and conversion rates for specified goals from Yandex.Metrica. It is clear what the tool does, but it does not explicitly differentiate itself from sibling tools such as get_metrika_goals or get_metrika_conversion_rate_by_source_and_landing.

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?

The description gives no guidance on when to use this tool versus alternatives, nor does it mention prerequisites such as obtaining goal_ids from get_metrika_goals. Usage is only implied by the purpose statement.

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?