PR-CY MCP

get_serp

Получить результаты поисковой системы по ключевой фразе.

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": {
      "keyword": "<keyword>"
    },
    "name": "get_serp"
  }
}

Input Schema

Name	Required	Description	Default
`top`	No	Количество результатов
`device`	No	Устройство	desktop
`engine`	No	Поисковая система	google
`region`	No	Идентификатор региона
`keyword`	Yes	Ключевая фраза
`language`	No	Язык интерфейса	ru
`with_related_values`	No	Вернуть вместе с выдачей связанные вопросы и связанные поисковые запросы. Проверка с ними стоит в два раза дороже

Output Schema

Name	Required	Description
`serp`	Yes	Результаты поисковой выдачи
`task_id`	Yes	Идентификатор задачи, по которому открывается её страница
`related_searches`	No	Связанные поисковые запросы
`related_questions`	No	Связанные вопросы

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, but it says nothing about cost, rate limits, engine differences, or that the with_related_values flag doubles the price (that detail exists only in the schema). The one sentence is purely a restatement of purpose.

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?

A single short sentence with no wasted words and the object of the operation front-loaded. It is efficient but too thin to be exemplary.

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 rich schema plus an output schema relieve much of the burden, but for a 7-parameter external-SERP call the description could still flag cost, engine behavior, or region defaults. It is minimally adequate rather than complete.

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 every parameter including engine, region, device, and the cost-doubling with_related_values is documented in the schema already. The description adds no semantics beyond that, so baseline 3 applies.

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 ('Получить') and resource ('результаты поисковой системы') scoped by a key phrase, so the agent knows exactly what is produced. It does not name or differentiate against siblings such as get_wordstat or check_positions, which also return search-related data.

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?

There is no guidance on when to use this tool instead of the many sibling tools, and no mention of prerequisites such as API quota or which engine to pick. The only steering lives in the schema defaults, not in prose.

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?