SEO GSC Wizard MCP

Yandex query stats

get_yandex_query_stats

Read-only

Use this when the user asks which searches bring their site visitors from Yandex: Yandex Webmaster queries for a property, with impressions, clicks, average impression position and average clicked position. IMPORTANT COVERAGE LIMIT: Yandex exposes only its top queries for the period (at most 3,000), so totals from these rows are a floor, not a complete figure, and any share is of the listed queries, not of the site; 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, sorted by that metric, highest first; 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. Not for Google or Bing queries: use query_top_queries or get_bing_query_stats. 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

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

Name	Required	Description
`hint`	No
`range`	No
`hostId`	No
`reason`	No
`thenBy`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`queries`	No
`siteUrl`	No
`nextStep`	No
`ordering`	No
`sortedBy`	No
`warnings`	No
`sortOrder`	No
`thenOrder`	No
`truncated`	No
`dataSource`	No
`deviceType`	No
`limitations`	No
`coverageNote`	No
`emptyBecause`	No
`methodLimits`	No
`notConfigured`	No
`totalAvailable`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedOutput schema / properties / listKey

Added value: +{
+  "$ref": "#/properties/siteUrl",
+  "description": "Name of the top-level field that holds the rows sortedBy describes."
+}

Changed11 schema fields changedOct 18, 2026

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / emptyBecause

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

addedOutput schema / properties / methodLimits

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

addedOutput schema / properties / nextStep

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

addedOutput schema / properties / ordering

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "additionalProperties": true,
+        "properties": {
+          "sortOrder": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "sortedBy": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "thenBy": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "thenOrder": {
+            "$ref": "#/properties/siteUrl"
+          }
+        },
+        "type": "object"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / queries / items / additionalProperties
```
Previous value: -falseNew value: +true
```

changedOutput schema / properties / range / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "endDate": {
-        "$ref": "#/properties/siteUrl"
-      },
-      "startDate": {
-        "$ref": "#/properties/siteUrl"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "endDate": {
+        "$ref": "#/properties/siteUrl"
+      },
+      "startDate": {
+        "$ref": "#/properties/siteUrl"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / sortOrder

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

addedOutput schema / properties / sortedBy

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

addedOutput schema / properties / thenBy

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

addedOutput schema / properties / thenOrder

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

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

A4.8/5.0

Behavior5/5

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

Goes far beyond the readOnly/openWorld annotations: discloses the top-3,000 coverage floor, 500-rows-per-request paging, that totals/shares are of listed queries not the site, CTR derivation and null case, absence of query-by-page attribution, a ~4-day data lag, and the full notConfigured/owner-only conditions. This is the kind of context annotations cannot carry.

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?

Well front-loaded (use-case, then IMPORTANT COVERAGE LIMIT, then mechanics), and nearly every sentence carries a distinct fact. It is dense and long, with some overlap between description and schema on limit/paging, but no filler sentences.

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

Completeness5/5

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

For a complex, caveat-heavy tool with an output schema, the description supplies everything an agent needs to call and report correctly: coverage limits, paging, lag, attribution limits, and the notConfigured contract. Return-shape detail is appropriately left to the output schema.

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 coverage is already 83%, but the description adds meaning beyond it: orderBy decides which 500 rows Yandex returns, dates select a real window with a last-week default, and 'range' echoes the actually-served window. Some parameter detail (limit ceiling behavior) largely restates the schema, keeping it just below 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (Yandex Webmaster queries for a property) and enumerates the metrics returned (impressions, clicks, avg impression position, avg clicked position). It explicitly distinguishes itself from get_bing_query_stats and query_top_queries, so an agent can route without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Front-loads the triggering user question ('which searches bring their site visitors from Yandex') and names the alternatives for Google/Bing ('use query_top_queries or get_bing_query_stats'). Also clarifies date defaults and the device-filter-vs-breakdown distinction, leaving little to infer.

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

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?