SEO GSC Wizard MCP

Yandex query stats

get_yandex_query_stats

Read-only

Search queries from Yandex Webmaster for a property, with impressions, clicks, average impression position and average clicked position. IMPORTANT COVERAGE LIMIT: Yandex exposes its top queries for the period, at most 3,000 of them, so totals derived from these rows are a floor, not a complete figure; say so when reporting them. Yandex serves 500 rows per request and this tool pages through as many as limit allows, defaulting to the first 500 by orderBy; totalAvailable and truncated say how much of the pool was left. CTR is a percentage (0-100, like every other CTR this server returns), calculated from impressions and clicks because Yandex publishes no CTR metric; null when there were no impressions. Yandex has no query-by-page report, so these queries cannot be attributed to URLs. The dates select a real window, so a longer range returns more queries and larger totals; omitting them gives the last week only. Yandex finishes a day about four days late, so range echoes the window it actually served. The full set of caveats is in limitations on every response. Returns notConfigured: true (with a reason) when no Yandex account is connected, the connection has to be granted again, the property is not in it, or the caller holds a share of the property rather than owning it: Yandex data is owner-only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Rows to return, across pages. Yandex serves 500 per request and at most 3,000 for a window, so a limit above 500 costs one extra round trip per 500 rows. The default is one page: ask for more only when the long tail matters, since a few thousand rows can exceed a host response-size ceiling and be refused.
`endDate`	No	End date (YYYY-MM-DD). Defaults to the last week Yandex holds.
`orderBy`	No	Which metric decides the 500 queries Yandex returns.	TOTAL_SHOWS
`siteUrl`	Yes
`startDate`	No	Start date (YYYY-MM-DD). Defaults to the last week Yandex holds.
`deviceType`	No	Device filter. Yandex filters rather than breaking down by device, so each value is a separate query. MOBILE_AND_TABLET overlaps MOBILE and TABLET, so do not sum them.	ALL

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hint`	No
`range`	No
`hostId`	No
`reason`	No
`queries`	No
`siteUrl`	No
`warnings`	No
`truncated`	No
`dataSource`	No
`deviceType`	No
`limitations`	No
`coverageNote`	No
`notConfigured`	No
`totalAvailable`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 10, 2026

changedInput schema / properties / limit / description

Previous value: -"Rows to return, across pages. Yandex serves 500 per request and holds 3,000, so a limit above 500 costs one extra round trip per 500 rows. The default is one page: ask for more only when the long tail matters, since a few thousand rows can exceed a host response-size ceiling and be refused."New value: +"Rows to return, across pages. Yandex serves 500 per request and at most 3,000 for a window, so a limit above 500 costs one extra round trip per 500 rows. The default is one page: ask for more only when the long tail matters, since a few thousand rows can exceed a host response-size ceiling and be refused."

Changed2 schema fields changedOct 10, 2026

addedOutput schema / properties / reason

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / warnings

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed3 schema fields changedOct 8, 2026

changedInput schema / properties / deviceType / description

Previous value: -"Device filter. Yandex filters rather than breaking down by device, so each value is a separate query. MOBILE_AND_TABLET overlaps MOBILE and TABLET — do not sum them."New value: +"Device filter. Yandex filters rather than breaking down by device, so each value is a separate query. MOBILE_AND_TABLET overlaps MOBILE and TABLET, so do not sum them."

addedInput schema / properties / limit / description

Added value: +"Rows to return, across pages. Yandex serves 500 per request and holds 3,000, so a limit above 500 costs one extra round trip per 500 rows. The default is one page: ask for more only when the long tail matters, since a few thousand rows can exceed a host response-size ceiling and be refused."

changedInput schema / properties / limit / maximum
```
Previous value: -500New value: +3000
```

Changed1 schema field changedOct 8, 2026

addedOutput schema / properties / limitations

Added value: +{
+  "items": {
+    "$ref": "#/properties/siteUrl"
+  },
+  "type": "array"
+}

First observedOct 7, 2026

TDQS

Score is being calculated.

All SEO GSC Wizard 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?