PR-CY MCP

get_keywords_pages_summary

Получить сводку по ключевым словам и страницам с расширенными фильтрами из Google Search Console и/или Яндекс.Вебмастер.

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_keywords_pages_summary"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	JSON-объект фильтра по URL. Формат: {"value": "<строка>", "compare_type": "equals\|notEquals\|startsWith\|endsWith\|contains\|notContains\|regex"}. compare_type опционален, по умолчанию contains. Для regex используется синтаксис RE2.
`sort`	No	Сортировка. Формат: поле1,-поле2 (- означает убывание). Пример: -impressions,ctr. Поля можно указывать в camelCase или snake_case (diffClicks и diff_clicks эквивалентны).	-impressions
`limit`	No	Количество элементов на странице
`offset`	No	Смещение элементов
`source`	No	Источник данных: gsc, webmaster или all.	all
`date_to`	No	Дата окончания периода. Формат YYYY-MM-DD. Должна быть не позже (today - 3 days). Если не указана, используется (today - 3 days). Должна быть >= date_from. Пример: 2024-02-28.
`keyword`	No	JSON-объект фильтра по ключевому слову. Формат: {"value": "<строка>", "compare_type": "equals\|notEquals\|startsWith\|endsWith\|contains\|notContains\|regex"}. compare_type опционален, по умолчанию contains. Для regex используется синтаксис RE2.
`date_from`	No	Дата начала периода. Формат YYYY-MM-DD. Должна быть не позже (today - 3 days). Если не указана, используется (today - 13 days). Должна быть <= date_to. Пример: 2024-02-26.
`project_id`	Yes	Идентификатор проекта.
`prev_date_to`	No	Дата окончания предыдущего периода. Формат YYYY-MM-DD. Обязательна вместе с prev_date_from. Должна быть не позже (today - 3 days) и >= prev_date_from. Пример: 2024-02-24.
`metrics_filter`	No	Диапазонный фильтр по метрикам
`prev_date_from`	No	Дата начала предыдущего периода. Формат YYYY-MM-DD. Обязательна вместе с prev_date_to. Должна быть не позже (today - 3 days) и <= prev_date_to. Пример: 2024-02-22.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

C2.9/5.0

Behavior2/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, yet it only states that data is retrieved. It omits read-only assumptions, permissions/auth, rate limits, pagination behavior, date-range defaults, and whether source='all' merges or compares GSC/webmaster data.

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 definition is a single front-loaded sentence with no filler. It is compact, though its brevity contributes to missing usage and behavioral context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter, multi-source summary tool with many sibling summary tools and no annotations, the description is too thin: it does not route among alternatives or explain operational constraints. Output schema and full parameter docs reduce the need to explain return values, but not the need for usage 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 12 parameters. The description adds only a generic mention of 'advanced filters' and data sources, not filter syntax or defaults 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?

States a concrete verb ('Получить') and resource ('сводку по ключевым словам и страницам'), plus data sources. However, it does not distinguish this combined summary from siblings such as get_keywords_summaries, get_pages_summary, or get_pages_summary_by_dates.

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?

No explicit when/when-not guidance or alternative tool routing is provided. The mention of GSC/Yandex.Webmaster implies source scope but does not tell an agent when to choose this over the many similar summary tools.

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?