Skip to main content
Glama
Sign In

SEO GSC Wizard MCP

by com.gscwizard.mcp
OverviewDiscussionsAdmin

Get indexing tracker config + stats

get_indexing_tracker
Read-only

Use this when the user asks how many of their tracked URLs are indexed, or whether indexing tracking is set up. Returns the GSC Wizard Indexing Tracker configuration for a property plus summary stats (total tracked URLs, indexed / not-indexed / pending / error counts, active warnings, and the most recent check time). Returns tracker: null if no tracker is configured for the property. Not for the URLs themselves: use list_tracked_urls; for lost and newly indexed pages over time use get_indexing_tracker_report.

Input Schema

NameRequiredDescriptionDefault
siteUrlYes

Output Schema

NameRequiredDescriptionDefault
statsNo
messageNo
siteUrlNo
trackerNo
nextStepNo
emptyBecauseNo
methodLimitsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedOutput schema / 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"
+}
    • changedOutput schema / properties / stats / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "errors": {
-        "$ref": "#/properties/tracker/anyOf/0/properties/staleCrawlThresholdDays"
-      },
-      "indexed": {
-        "$ref": "#/properties/tracker/anyOf/0/properties/staleCrawlThresholdDays"
-      },
-      "lastCheckAt": {
-        "$ref": "#/properties/siteUrl"
-      },
-      "notIndexed": {
-        "$ref": "#/properties/tracker/anyOf/0/properties/staleCrawlThresholdDays"
-      },
-      "pending": {
-        "$ref": "#/properties/tracker/anyOf/0/properties/staleCrawlThresholdDays"
-      },
-      "total": {
-        "$ref": "#/properties/tracker/anyOf/0/properties/staleCrawlThresholdDays"
-      },
-      "warnings": {
-        "$ref": "#/properties/tracker/anyOf/0/properties/staleCrawlThresholdDays"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "errors": {
+        "$ref": "#/properties/tracker/anyOf/0/properties/staleCrawlThresholdDays"
+      },
+      "indexed": {
+        "$ref": "#/properties/tracker/anyOf/0/properties/staleCrawlThresholdDays"
+      },
+      "lastCheckAt": {
+        "$ref": "#/properties/siteUrl"
+      },
+      "notIndexed": {
+        "$ref": "#/properties/tracker/anyOf/0/properties/staleCrawlThresholdDays"
+      },
+      "pending": {
+        "$ref": "#/properties/tracker/anyOf/0/properties/staleCrawlThresholdDays"
+      },
+      "total": {
+        "$ref": "#/properties/tracker/anyOf/0/properties/staleCrawlThresholdDays"
+      },
+      "warnings": {
+        "$ref": "#/properties/tracker/anyOf/0/properties/staleCrawlThresholdDays"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / properties / tracker / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "createdAt": {
-        "$ref": "#/properties/siteUrl"
-      },
-      "emailDigestEnabled": {
-        "$ref": "#/properties/tracker/anyOf/0/properties/isActive"
-      },
-      "id": {
-        "$ref": "#/properties/siteUrl"
-      },
-      "isActive": {
-        "type": [
-          "boolean",
-          "null"
-        ]
-      },
-      "staleCrawlThresholdDays": {
-        "type": [
-          "number",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "createdAt": {
+        "$ref": "#/properties/siteUrl"
+      },
+      "emailDigestEnabled": {
+        "$ref": "#/properties/tracker/anyOf/0/properties/isActive"
+      },
+      "id": {
+        "$ref": "#/properties/siteUrl"
+      },
+      "isActive": {
+        "type": [
+          "boolean",
+          "null"
+        ]
+      },
+      "staleCrawlThresholdDays": {
+        "type": [
+          "number",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the exact stat categories returned and the important edge case that 'tracker: null' is returned when no tracker is configured. It stops short of richer operational detail (rate limits, quota behavior), keeping it at a 4.

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?

Four sentences, zero waste, and correctly front-loaded: trigger conditions first, then return contents, then the null edge case, then exclusions. The ordering maps directly onto how an agent decides to call and interpret the result.

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 structure need not be re-explained, yet the description still summarizes the returned counts and the null case. Together with the explicit sibling routing, an agent has everything needed to select and invoke the tool correctly.

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% for the single siteUrl parameter, so the description must compensate. It only indirectly conveys meaning via 'tracker configuration for a property', which implies siteUrl identifies a property but doesn't state format or expectations. Partial compensation for a one-param tool, hence baseline-ish 3 rather than 4.

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 (returns the GSC Wizard Indexing Tracker config + stats for a property) and names the exact trigger scenarios ('how many tracked URLs are indexed', 'whether indexing tracking is set up'). It explicitly distinguishes itself from list_tracked_urls and get_indexing_tracker_report, so an agent can route correctly 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?

Front-loads the 'use this when' conditions and then names two sibling alternatives with the conditions that select them ('Not for the URLs themselves: use list_tracked_urls', 'for lost and newly indexed pages over time use get_indexing_tracker_report'). Both when-to-use and when-not-to-use are explicit.

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 toolsInspect
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