SEO GSC Wizard MCP

Yandex site summary

get_yandex_site_summary

Read-only

Use this when the user asks how their site stands in Yandex: Yandex Webmaster's site quality index (SQI), pages in search, excluded pages, and the problems Yandex currently reports, counted by severity and listed most severe first (FATAL, CRITICAL, POSSIBLE_PROBLEM, RECOMMENDATION). Complements Google Search Console with the Yandex side of organic search, which matters for Russian, Turkish, Kazakh, Belarusian and Uzbek traffic. Not for Google performance: use get_site_summary. SQI and the problem severities are Yandex's own taxonomy with no Google equivalent, and Yandex serves no previous-period series, so there is nothing to compare against: the response carries these caveats in limitations, which should be passed on when reporting the numbers. When the problem list could not be read (a Yandex rate limit or timeout), problems is empty and warnings says so. 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
`siteUrl`	Yes

Output Schema

Name	Required	Description
`sqi`	No
`hint`	No
`hostId`	No
`reason`	No
`thenBy`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`siteUrl`	No
`nextStep`	No
`ordering`	No
`problems`	No
`sortedBy`	No
`warnings`	No
`sortOrder`	No
`thenOrder`	No
`dataSource`	No
`limitations`	No
`emptyBecause`	No
`methodLimits`	No
`excludedPages`	No
`notConfigured`	No
`pagesInSearch`	No
`problemCountsBySeverity`	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."
+}

Changed12 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"
+    }
+  ]
+}

addedOutput schema / properties / problems / anyOf

Added value: +[
+  {
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "code": {
+          "$ref": "#/properties/siteUrl"
+        },
+        "lastChangedAt": {
+          "$ref": "#/properties/siteUrl"
+        },
+        "severity": {
+          "$ref": "#/properties/siteUrl"
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / problems / items

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "code": {
-      "$ref": "#/properties/siteUrl"
-    },
-    "lastChangedAt": {
-      "$ref": "#/properties/siteUrl"
-    },
-    "severity": {
-      "$ref": "#/properties/siteUrl"
-    }
-  },
-  "type": "object"
-}

removedOutput schema / properties / problems / type
```
Removed value: -"array"
```

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

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"
+    }
+  ]
+}

Changed1 schema field changedOct 8, 2026

addedOutput schema / properties / limitations

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

First observedOct 7, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: it discloses that Yandex has no previous-period series and that the response flags this in `limitations`, that a rate limit or timeout yields an empty `problems` with an explanatory `warnings`, and that `notConfigured: true` plus a `reason` appears for four distinct auth/property/ownership cases. The owner-only access constraint is a genuinely useful behavioral detail.

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?

Front-loaded with the use case, then alternatives, then caveats, then error states – a sensible order. It is dense and long for a one-parameter read tool; a couple of clauses (e.g. the enumeration of markets) could be trimmed, but no sentence is filler.

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?

Despite an output schema, it proactively explains the non-obvious response shapes an agent must relay: `limitations`, empty `problems` on rate limit, and `notConfigured` with `reason`. The only meaningful gap is how to construct `siteUrl`, which is the one thing required to invoke the tool.

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?

The single parameter `siteUrl` has no description in the schema (0% coverage), and the description never explains its expected format (e.g. host vs full URL vs Yandex's site identifier) or whether it must match an existing Yandex Webmaster property. The call out about property ownership partially hints at this, but the parameter itself is left ambiguous.

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+resource (site quality standing in Yandex Webmaster) and enumerates exactly what is returned: SQI, pages in search, excluded pages, and problems by severity. It explicitly contrasts itself with get_site_summary for the Google side, so an agent can pick it without opening the schema.

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?

Gives the triggering condition ('when the user asks how their site stands in Yandex') and an explicit exclusion with the alternative tool named ('Not for Google performance: use get_site_summary'). It also scopes the audience via the markets Yandex serves (Russian, Turkish, Kazakh, Belarusian, Uzbek traffic).

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?