mowteng

Yandex search performance

yandex_search_queries

Read-only

Yandex's most popular search queries for a site, with impressions (shows), clicks and average show and click positions. Yandex keeps a limited history; the actual period is in the result. Paged with offset and limit.

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": {
      "hostId": "<hostId>"
    },
    "name": "yandex_search_queries"
  }
}

Input Schema

Name	Required	Description	Default
`sort`	No	Order by clicks or impressions, highest first. Defaults to clicks.	clicks
`limit`	No	Maximum items to return (1-500). Defaults to 50.
`device`	No	Device type. Defaults to ALL.	ALL
`hostId`	Yes	Yandex host_id exactly as yandex_list_sites returns it, e.g. "https:example.com:443"
`offset`	No	Number of items to skip, for paging. Defaults to 0.
`endDate`	No	End date, YYYY-MM-DD. Omit for Yandex's default, the last week.
`startDate`	No	Start date, YYYY-MM-DD. Omit for Yandex's default, the last week.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world, so the description only needs to add behaviour beyond that. It does: Yandex keeps a limited history and the actual period is reported in the result, which warns the agent that requested dates may not be honoured. Return format details beyond the metric names are still omitted.

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?

Three short sentences, front-loaded with what the tool returns. The final sentence about offset/limit only restates the schema and is the weakest part, otherwise there is no waste.

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

Completeness4/5

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

For a 7-parameter read tool with no output schema, the description names the returned metrics and flags the history limitation, which is the main thing an agent could get wrong. Missing only an explicit note on what the response envelope contains.

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 sort, limit, device, hostId, offset and dates with defaults and ranges. The description only echoes the paging mechanism (offset/limit) without adding syntax or constraints, 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?

States a specific verb+resource: the most popular search queries for a site, plus the metrics returned (impressions, clicks, average positions). This is clearly different from aggregate siblings like yandex_site_summary, but it never names or contrasts an alternative, so it stops short of a 5.

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?

Usage is implied by the resource ('popular search queries for a site'), but there is no explicit when-to-use, no exclusion criteria, and no routing to yandex_site_summary or gsc_search_analytics for adjacent needs. The agent must infer the choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mowteng 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.