SEO GSC Wizard MCP

Check tracked URLs now

check_tracked_url_now

Triggers an immediate Google URL Inspection for up to 10 tracked URLs in the GSC Wizard Indexing Tracker, updating each URL's status, warnings, and append-only history. Each result carries the Google-selected and user-declared canonicals (null when Google did not report one). Counts against the daily 2,000-inspection/property quota. If the quota is exhausted, the call returns a quota message instead of running. URLs are inspected five at a time (about 7 seconds each at Google). If Google rate-limits the property or refuses access to it, the URLs not yet inspected come back with skipped: true and a skipReason (plus retryAfterSeconds when Google gave one) and are left untouched; retry them later. Use sparingly; the app's hourly cron checks tracked URLs automatically. This is a server-side write and is audit-logged.

Input Schema

Name	Required	Description	Default
`urls`	Yes
`siteUrl`	Yes

Output Schema

Name	Required	Description	Default
`count`	No
`message`	No
`results`	No
`siteUrl`	No
`stopped`	No
`notChecked`	No
`quotaExhausted`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 18, 2026

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

changedOutput schema / properties / stopped / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "message": {
-        "$ref": "#/properties/siteUrl"
-      },
-      "reason": {
-        "$ref": "#/properties/siteUrl"
-      },
-      "retryAfterSeconds": {
-        "$ref": "#/properties/count"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "message": {
+        "$ref": "#/properties/siteUrl"
+      },
+      "reason": {
+        "$ref": "#/properties/siteUrl"
+      },
+      "retryAfterSeconds": {
+        "$ref": "#/properties/count"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed7 schema fields changedOct 10, 2026

addedOutput schema / properties / notChecked

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

addedOutput schema / properties / results / items / properties / googleCanonical
```
Added value: +{
+  "$ref": "#/properties/siteUrl"
+}
```
addedOutput schema / properties / results / items / properties / inspectionResultLink
```
Added value: +{
+  "$ref": "#/properties/siteUrl"
+}
```
addedOutput schema / properties / results / items / properties / retryAfterSeconds
```
Added value: +{
+  "$ref": "#/properties/count"
+}
```
addedOutput schema / properties / results / items / properties / skipReason
```
Added value: +{
+  "$ref": "#/properties/siteUrl"
+}
```
addedOutput schema / properties / results / items / properties / userCanonical
```
Added value: +{
+  "$ref": "#/properties/siteUrl"
+}
```

addedOutput schema / properties / stopped

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "message": {
+          "$ref": "#/properties/siteUrl"
+        },
+        "reason": {
+          "$ref": "#/properties/siteUrl"
+        },
+        "retryAfterSeconds": {
+          "$ref": "#/properties/count"
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

First observedOct 7, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly=false, destructive=false, openWorld=true), and the description adds substantial behavior beyond them: the 2,000-inspection daily quota and its exhaustion response, 5-at-a-time batching at ~7s each, rate-limit handling via skipped/retryAfterSeconds, untouched-on-skip semantics, and audit-logging. This is exactly the operational context an agent needs before invoking a quota-consuming write.

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?

Though dense at roughly six sentences, the purpose is front-loaded and each subsequent sentence conveys distinct operational detail (quota, batching, skip semantics), so little is wasted. It is information-rich rather than padded.

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 not be enumerated, yet the description still flags the canonical fields and null case. Combined with the quota, rate-limit, and audit-logging behavior, an agent has everything needed to call this correctly and interpret partial 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 description coverage is 0%, so the description must carry parameter meaning. It partially does: 'up to 10 tracked URLs' clarifies the urls array bound, and 'per property' hints that siteUrl is the GSC property. But neither parameter's format or accepted values is explained, so the schema remains largely silent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource: triggering an immediate Google URL Inspection for up to 10 tracked URLs, plus the side effect of updating status, warnings, and history. It scopes to 'tracked URLs in the GSC Wizard Indexing Tracker,' which implicitly separates it from generic inspect_url/bulk_inspect_urls, though those siblings are not named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use sparingly; the app's hourly cron checks tracked URLs automatically' gives a clear when-to-use constraint and an implicit when-not (don't manually re-run what the cron covers). However, it never names inspect_url or bulk_inspect_urls as alternatives, so the routing between inspection tools is left to inference.

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?