SEO GSC Wizard MCP

List saved migrations

list_migrations

Read-only

Use this when the user asks which site migrations they have saved, or a migrationId is needed. Lists the migrations saved on the account in the GSC Wizard app (Migration Compare), most recently updated first (updatedAt descending): id, name, mode (cross-property, two-urls or regex), the old (siteUrlA) and new (siteUrlB) property, go-live date, window settings, the redirect-mapping label, whether daily re-check alerts are on, and the last health snapshot from that re-check (status, recoveryPct, 0-100 risk score, redirect problem counts). Pass an id to get_migration_health as migrationId for the full analysis. Not for traffic figures: use get_migration_health or compare_migration. Takes no arguments.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`note`	No
`total`	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
`truncated`	No
`migrations`	No
`emptyBecause`	No
`methodLimits`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedOutput schema / properties / listKey

Added value: +{
+  "$ref": "#/properties/migrations/items/properties/id",
+  "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/migrations/items/properties/id"
+}

addedOutput schema / properties / methodLimits

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

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

addedOutput schema / properties / nextStep

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

addedOutput schema / properties / ordering

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

addedOutput schema / properties / sortOrder

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

addedOutput schema / properties / sortedBy

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

addedOutput schema / properties / thenBy

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

addedOutput schema / properties / thenOrder

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

AddedOct 11, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds non-obvious behavior the annotations can't: result ordering (updatedAt descending), the exact payload contents including the health snapshot fields, and the zero-argument nature of the call. No auth or rate-limit context, but that is minor for a read-only list.

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 this when' trigger sentence, then the payload, then the routing follow-up. The middle field-enumeration sentence is long and dense, but each item listed is a real datum an agent would otherwise have to guess at, so it largely earns its place.

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?

Even though an output schema exists, the description still surfaces the salient return fields and their semantics (mode values, 0-100 risk score, recoveryPct) so an agent can decide whether to call it. Combined with ordering, zero-arg confirmation, and the handoff to get_migration_health, nothing needed to call this 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?

The tool takes zero parameters, which sets the baseline at 4. 'Takes no arguments' explicitly closes the loop and prevents an agent from hunting for filter options — a small but real clarification, though it restates what an empty schema already shows.

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 the migrations saved on the account in the GSC Wizard app'), scopes it to Migration Compare, and distinguishes it from migration siblings like compare_migration and get_migration_health. The enumeration of returned fields makes the tool's identity unambiguous.

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 an explicit trigger ('when the user asks which site migrations they have saved, or a migrationId is needed'), an explicit exclusion ('Not for traffic figures: use get_migration_health or compare_migration'), and a follow-up route ('Pass an id to get_migration_health as migrationId'). All three alternatives are named with conditions.

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?