PR-CY MCP

get_metrika_conversion_rate_by_source_and_landing

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

Input Schema

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

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the default 7-day date range when dates are omitted, but it does not state that this is a read-only analytics query, nor does it mention permissions, data freshness, or limitations.

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

Conciseness4/5

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

The description is three sentences and front-loads the tool's purpose. The second sentence adds useful context about the analytical value, and the third sentence efficiently documents the default date behavior.

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 description covers purpose, benefit, and default date behavior, and the output schema means return values need not be explained. However, for a tool in a crowded Metrika toolset with no annotations, it lacks sibling-selection guidance and basic behavioral details such as read-only status.

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 parameter baseline is 3. The description adds meaningful semantics beyond the schema by explaining that unspecified dates default to the last 7 days, which affects how date_from and date_to are used.

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 action and resource: obtaining conversion-rate analysis by traffic source and landing page from Yandex.Metrika. It is clearly distinct from generic goals conversion or sources summary tools, but it does not explicitly name a sibling alternative or exclusion.

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 description provides an implied use case: understanding which traffic sources drive conversions on specific landing pages. However, it gives no explicit guidance on when to use this tool versus sibling Metrika tools such as get_metrika_goals_conversion or get_metrika_sources_summary.

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?