SEO GSC Wizard MCP

Delete migration redirect mappings

delete_migration_redirects

Destructive

Permanently deletes saved redirect mappings. Narrow the deletion with label and/or the A/B property pair; to delete EVERY mapping on the account you must pass confirmDeleteAll: true, since an unnarrowed delete would also wipe unrelated migrations. Preview exactly what would go with list_migration_redirects using the same filters first.

Input Schema

Name	Required	Description
`label`	No	Only mappings carrying this label.
`siteUrlA`	No	Only mappings whose source property is this.
`siteUrlB`	No	Only mappings whose target property is this.
`confirmDeleteAll`	No	Required when no label or property filter is given: deletes every mapping.

Output Schema

Name	Required	Description	Default
`deleted`	No
`filters`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 18, 2026

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

changedOutput schema / properties / filters / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "deletedAll": {
-        "type": [
-          "boolean",
-          "null"
-        ]
-      },
-      "label": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "siteUrlA": {
-        "$ref": "#/properties/filters/anyOf/0/properties/label"
-      },
-      "siteUrlB": {
-        "$ref": "#/properties/filters/anyOf/0/properties/label"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "deletedAll": {
+        "type": [
+          "boolean",
+          "null"
+        ]
+      },
+      "label": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "siteUrlA": {
+        "$ref": "#/properties/filters/anyOf/0/properties/label"
+      },
+      "siteUrlB": {
+        "$ref": "#/properties/filters/anyOf/0/properties/label"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedOct 7, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, but the description goes further: it discloses that deletion is permanent, that an unnarrowed delete would also wipe unrelated migrations, and that confirmDeleteAll: true is a hard prerequisite for that path. This is exactly the collateral-damage and safety-guard context annotations cannot convey.

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?

Three sentences, front-loaded with the destructive nature and scope, then the narrowing/guard rule, then the recommended preview step. Every sentence carries decision-relevant information with no padding.

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?

An output schema exists so return values need no explanation. The description covers purpose, scope, all four parameters' roles, the destructive guard, and the safe workflow, which is everything an agent needs to invoke this correctly.

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 the baseline is 3, but the description adds real meaning beyond the schema: it explains the coupling between the filter params and confirmDeleteAll, and why the guard exists (unrelated migrations would be destroyed). It does not add format or syntax detail beyond that.

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 ('Permanently deletes saved redirect mappings') and is immediately distinguishable from the sibling add_migration_redirects and the read-only list_migration_redirects. No ambiguity about what operation is performed.

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?

Explicitly routes the agent: narrow with `label` and/or the A/B property pair, pass confirmDeleteAll: true only for a full-account wipe, and preview with list_migration_redirects using the same filters first. Names both the required guard condition and the recommended alternative tool.

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?