SEO GSC Wizard MCP

List Google algorithm updates

list_algo_updates

Read-only

Use this when the user asks which Google core, spam or other ranking updates rolled out in a period. Fetches confirmed Google ranking/algorithm updates from the official Search Status Dashboard. Filters to service_name="Ranking" so indexing/crawling incidents are excluded. Optionally clip to a date range: an update is included when its rollout (beginISO to endISO) overlaps the range, so one that started before startDate but was still rolling out inside it is listed. The feed is cached for 15 minutes. Not for the user's own chart notes: use list_annotations. Newest first (beginISO descending).

Input Schema

Name	Required	Description	Default
`endDate`	No	Optional filter: only include updates that began on or before this date (YYYY-MM-DD). Omit to include all. Never pass null or "null".
`startDate`	No	Optional filter: only include updates still rolling out on or after this date (YYYY-MM-DD). Omit to include all. Never pass null or "null".

Output Schema

Name	Required	Description
`thenBy`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`updates`	No
`nextStep`	No
`ordering`	No
`sortedBy`	No
`sortOrder`	No
`thenOrder`	No
`emptyBecause`	No
`methodLimits`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 28, 2026

addedOutput schema / properties / listKey

Added value: +{
+  "description": "Name of the top-level field that holds the rows sortedBy describes.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / sortedBy / $ref
```
Added value: +"#/properties/listKey"
```
removedOutput schema / properties / sortedBy / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

Changed17 schema fields changedOct 18, 2026

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

addedOutput schema / properties / emptyBecause

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

addedOutput schema / properties / methodLimits

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

addedOutput schema / properties / nextStep

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

addedOutput schema / properties / ordering

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

addedOutput schema / properties / sortOrder

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

addedOutput schema / properties / sortedBy

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

addedOutput schema / properties / thenBy

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

addedOutput schema / properties / thenOrder

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

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

changedOutput schema / properties / updates / items / properties / beginISO / $ref

Previous value: -"#/properties/updates/items/properties/id"New value: +"#/properties/sortedBy"

changedOutput schema / properties / updates / items / properties / endISO / $ref

Previous value: -"#/properties/updates/items/properties/id"New value: +"#/properties/sortedBy"

addedOutput schema / properties / updates / items / properties / id / $ref
```
Added value: +"#/properties/sortedBy"
```
removedOutput schema / properties / updates / items / properties / id / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

changedOutput schema / properties / updates / items / properties / name / $ref

Previous value: -"#/properties/updates/items/properties/id"New value: +"#/properties/sortedBy"

changedOutput schema / properties / updates / items / properties / severity / $ref

Previous value: -"#/properties/updates/items/properties/id"New value: +"#/properties/sortedBy"

changedOutput schema / properties / updates / items / properties / uri / $ref

Previous value: -"#/properties/updates/items/properties/id"New value: +"#/properties/sortedBy"

Changed2 schema fields changedOct 10, 2026

changedInput schema / properties / endDate / description

Previous value: -"Optional filter: only include updates on or before this date (YYYY-MM-DD). Omit to include all. Never pass null or \"null\"."New value: +"Optional filter: only include updates that began on or before this date (YYYY-MM-DD). Omit to include all. Never pass null or \"null\"."

changedInput schema / properties / startDate / description

Previous value: -"Optional filter: only include updates on or after this date (YYYY-MM-DD). Omit to include all. Never pass null or \"null\"."New value: +"Optional filter: only include updates still rolling out on or after this date (YYYY-MM-DD). Omit to include all. Never pass null or \"null\"."

First observedOct 7, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations only declare readOnly/openWorld/non-destructive; the description adds real behavioral context beyond that: the upstream source, the hard-coded service_name filter that silently drops indexing incidents, the 15-minute feed cache, and the newest-first ordering. It does not discuss failure modes or whether a stale cache can omit a just-announced update, which keeps it short of a 5.

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?

Trigger sentence first, then scope, then filter semantics, then cache/sort behavior, then the exclusion — front-loaded with zero filler. Every sentence carries information an agent could otherwise get wrong.

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 an output schema present, return values need no explanation; the description instead covers source, filtering, range semantics, caching, ordering, and sibling routing. Nothing needed to invoke it correctly 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?

Schema coverage is 100%, so baseline is 3, but the description adds the non-obvious overlap rule: 'an update is included when its rollout (beginISO to endISO) overlaps the range,' so an update that began before startDate but was still rolling out is returned. This resolves the intuition that endDate means 'began on or before' into interval-overlap semantics.

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 ('Fetches confirmed Google ranking/algorithm updates from the official Search Status Dashboard') and pins the scope with service_name="Ranking" so indexing/crawling incidents are excluded. An agent can distinguish this from generic listing siblings 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?

Opens with an explicit trigger ('Use this when the user asks which Google core, spam or other ranking updates rolled out in a period') and explicitly excludes a confusing alternative: 'Not for the user's own chart notes: use list_annotations.' Both the when and the when-not are named.

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?