SEO GSC Wizard MCP

Yandex sites

list_yandex_sites

Read-only

Use this when the user asks which of their sites have Yandex data, or which sites their Yandex Webmaster account holds. Lists the sites in the connected Yandex Webmaster account, with their verification status and the canonical mirror Yandex resolved for each, sorted by url (A to Z). Only sites already added AND verified in Yandex Webmaster itself report data. Not for Search Console or Bing properties: use list_sites or list_bing_sites. The list is cached for ten minutes. Returns notConfigured: true when no Yandex account is connected, or when the connection has to be granted again (reason: reauth).

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`hint`	No
`sites`	No
`reason`	No
`thenBy`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`nextStep`	No
`ordering`	No
`sortedBy`	No
`sortOrder`	No
`thenOrder`	No
`dataSource`	No
`limitations`	No
`emptyBecause`	No
`methodLimits`	No
`notConfigured`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedOutput schema / properties / listKey

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

Changed10 schema fields changedOct 18, 2026

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

addedOutput schema / properties / emptyBecause

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

addedOutput schema / properties / methodLimits

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

addedOutput schema / properties / nextStep

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

addedOutput schema / properties / ordering

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

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

addedOutput schema / properties / sortOrder

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

addedOutput schema / properties / sortedBy

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

addedOutput schema / properties / thenBy

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

addedOutput schema / properties / thenOrder

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

Changed1 schema field changedOct 10, 2026
- addedOutput schema / properties / reason
```
Added value: +{
+  "$ref": "#/properties/limitations/items"
+}
```

Changed8 schema fields changedOct 8, 2026

changedOutput schema / properties / dataSource / $ref

Previous value: -"#/properties/sites/items/properties/hostId"New value: +"#/properties/limitations/items"

changedOutput schema / properties / hint / $ref

Previous value: -"#/properties/sites/items/properties/hostId"New value: +"#/properties/limitations/items"

addedOutput schema / properties / limitations

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

addedOutput schema / properties / sites / items / properties / hostId / $ref
```
Added value: +"#/properties/limitations/items"
```
removedOutput schema / properties / sites / items / properties / hostId / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

changedOutput schema / properties / sites / items / properties / mainMirrorUrl / $ref

Previous value: -"#/properties/sites/items/properties/hostId"New value: +"#/properties/limitations/items"

changedOutput schema / properties / sites / items / properties / unicodeUrl / $ref

Previous value: -"#/properties/sites/items/properties/hostId"New value: +"#/properties/limitations/items"

changedOutput schema / properties / sites / items / properties / url / $ref

Previous value: -"#/properties/sites/items/properties/hostId"New value: +"#/properties/limitations/items"

First observedOct 7, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld/non-destructive annotations by disclosing the ten-minute cache, the notConfigured:true failure mode with reason:'reauth', and the constraint that only sites added AND verified in Yandex Webmaster report data — all traits an agent cannot infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences, front-loaded with the trigger, followed by scope, exclusions, and operational caveats. No sentence is redundant and each adds a distinct fact.

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?

With annotations covering the safety profile, an output schema covering return shape, and zero parameters, the description fills the remaining gaps (caching, not-configured behavior, verified-only constraint) thoroughly. Nothing needed to call or interpret the tool is missing.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter semantics to explain. The description usefully notes the sort order of the result set, which is a small value-add beyond the empty schema.

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 (lists sites in the connected Yandex Webmaster account) and enriches it with the returned attributes (verification status, canonical mirror) and ordering. It also explicitly names the siblings it is not: list_sites and list_bing_sites.

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?

Opens with an explicit trigger ('Use this when the user asks which of their sites have Yandex data') and closes with an explicit exclusion routing to list_sites/list_bing_sites. When-to-use, when-not, and alternatives are all present.

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?