SEO GSC Wizard MCP

Yandex indexing history

get_yandex_indexing_history

Read-only

Use this when the user asks how Yandex crawls and indexes their site over time: the HTTP status codes Yandex's crawler received by day, how many pages are in Yandex search, and the count of pages that appeared in or were removed from Yandex results each day. Use the appeared/removed series to spot day-to-day swings in which pages Yandex indexes. Every series runs oldest day first; crawlResponses are ordered by status and searchAppearanceChanges by event. Not for Google indexing or Bing crawling: use get_indexing_tracker or get_bing_crawl_stats. These series carry no country or device dimension and no previous-period comparison; the response repeats that in limitations. When one of the two secondary series could not be read (a Yandex rate limit or timeout), it comes back 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
`endDate`	No	End date (YYYY-MM-DD). Defaults to what Yandex returns by default.
`siteUrl`	Yes
`startDate`	No	Start date (YYYY-MM-DD). Defaults to what Yandex returns by default.

Output Schema

Name	Required	Description
`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
`sortedBy`	No
`warnings`	No
`sortOrder`	No
`thenOrder`	No
`dataSource`	No
`limitations`	No
`emptyBecause`	No
`methodLimits`	No
`notConfigured`	No
`pagesInSearch`	No
`crawlResponses`	No
`searchAppearanceChanges`	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."
+}

Changed17 schema fields changedOct 18, 2026

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
changedOutput schema / properties / crawlResponses / items / additionalProperties
```
Previous value: -falseNew value: +true
```
changedOutput schema / properties / crawlResponses / items / properties / points / items / 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 / pagesInSearch / anyOf

Added value: +[
+  {
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "date": {
+          "$ref": "#/properties/siteUrl"
+        },
+        "value": {
+          "$ref": "#/properties/crawlResponses/items/properties/points/items/properties/value"
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / pagesInSearch / items

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "date": {
-      "$ref": "#/properties/siteUrl"
-    },
-    "value": {
-      "$ref": "#/properties/crawlResponses/items/properties/points/items/properties/value"
-    }
-  },
-  "type": "object"
-}

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

addedOutput schema / properties / searchAppearanceChanges / anyOf

Added value: +[
+  {
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "event": {
+          "$ref": "#/properties/siteUrl"
+        },
+        "points": {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "date": {
+                "$ref": "#/properties/siteUrl"
+              },
+              "value": {
+                "$ref": "#/properties/crawlResponses/items/properties/points/items/properties/value"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "points"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / searchAppearanceChanges / items

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "event": {
-      "$ref": "#/properties/siteUrl"
-    },
-    "points": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "date": {
-            "$ref": "#/properties/siteUrl"
-          },
-          "value": {
-            "$ref": "#/properties/crawlResponses/items/properties/points/items/properties/value"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "points"
-  ],
-  "type": "object"
-}

removedOutput schema / properties / searchAppearanceChanges / 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.6/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), and the description layers on substantive behavior: series ordering (oldest day first, sorted by status/event), the absence of country/device dimensions and period comparisons, degraded-read behavior (empty series plus `warnings` on rate limit/timeout), and notConfigured semantics with owner-only auth as an explicit precondition.

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?

Purpose and trigger are front-loaded, and the alternative routing arrives before the edge-case details. It is dense but nearly every clause carries operational value; a few phrasings (e.g., 'the response repeats that in `limitations`') could be trimmed without losing meaning.

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 read-only, three-parameter tool with an output schema, the description covers everything an agent needs: what comes back, ordering, known limitations, partial-failure signaling, and the full set of notConfigured conditions. No gaps remain that would cause a mis-call or a misread of results.

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 coverage is 67%: startDate and endDate are documented in the schema, while siteUrl has no description and the tool description only hints at it via 'the property is not in it'. Beyond that the description adds little parameter-level meaning (no format or range guidance for dates), so it neither compensates for nor significantly extends the 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?

Declares a specific verb and resource ('how Yandex crawls and indexes their site over time') and enumerates the three concrete series returned: daily HTTP status codes, pages in Yandex search, and appeared/removed counts. It explicitly names the sibling tools it is not (get_indexing_tracker, get_bing_crawl_stats), so an agent can disambiguate 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?

Opens with an explicit triggering condition ('Use this when the user asks how Yandex crawls and indexes their site over time') and adds a secondary use case ('use the appeared/removed series to spot day-to-day swings'). It also states exclusions and routes the agent to the correct alternatives for Google and Bing data.

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?