SEO GSC Wizard MCP

Indexing tracker health report

get_indexing_tracker_report

Read-only

Use this when the user asks how indexing of their tracked URLs is trending, including lost or newly indexed pages; it covers tracker URLs only. Indexing-health report for a property over the last N days (default 30, max 90). Computes a 0-100 health score from indexed %, crawl freshness, and warning-free % (each 0-100), plus a coverage-state breakdown, crawl-freshness buckets, recently lost pages, and newly indexed pages (newest first, max 200; lostPagesTotal / newlyIndexedTotal count all). A property with no tracker yet answers configured: false with empty figures; add URLs with add_tracked_urls to start one. Not for the per-URL list: use list_tracked_urls.

Input Schema

Name	Required	Description	Default
`days`	No
`siteUrl`	Yes

Output Schema

Name	Required	Description
`days`	No
`thenBy`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`message`	No
`siteUrl`	No
`nextStep`	No
`ordering`	No
`sortedBy`	No
`breakdown`	No
`lostPages`	No
`sortOrder`	No
`thenOrder`	No
`truncated`	No
`configured`	No
`healthScore`	No
`emptyBecause`	No
`methodLimits`	No
`newlyIndexed`	No
`crawlFreshness`	No
`lostPagesTotal`	No
`coverageBreakdown`	No
`newlyIndexedTotal`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedOutput schema / properties / listKey

Added value: +{
+  "$ref": "#/properties/siteUrl",
+  "description": "Name of the top-level field that holds the rows sortedBy describes."
+}

Changed14 schema fields changedOct 18, 2026

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

changedOutput schema / properties / breakdown / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "freshCrawlPercent": {
-        "$ref": "#/properties/days"
-      },
-      "indexedPercent": {
-        "$ref": "#/properties/days"
-      },
-      "totalTracked": {
-        "$ref": "#/properties/days"
-      },
-      "warningCount": {
-        "$ref": "#/properties/days"
-      },
-      "warningFreePercent": {
-        "$ref": "#/properties/days"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "freshCrawlPercent": {
+        "$ref": "#/properties/days"
+      },
+      "indexedPercent": {
+        "$ref": "#/properties/days"
+      },
+      "pendingCount": {
+        "$ref": "#/properties/days"
+      },
+      "totalTracked": {
+        "$ref": "#/properties/days"
+      },
+      "warningCount": {
+        "$ref": "#/properties/days"
+      },
+      "warningFreePercent": {
+        "$ref": "#/properties/days"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / emptyBecause

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

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

addedOutput schema / properties / lostPagesTotal

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

addedOutput schema / properties / methodLimits

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

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

addedOutput schema / properties / newlyIndexedTotal

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

addedOutput schema / properties / nextStep

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

addedOutput schema / properties / ordering

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

addedOutput schema / properties / sortOrder

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

addedOutput schema / properties / sortedBy

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

addedOutput schema / properties / thenBy

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

addedOutput schema / properties / thenOrder

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

Changed3 schema fields changedOct 10, 2026

addedOutput schema / properties / configured

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

addedOutput schema / properties / message

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

addedOutput schema / properties / truncated

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

First observedOct 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/openWorld=false, but the description goes well beyond them: it discloses the default and cap on the window (30/90), how the 0-100 health score is composed, the breakdowns returned, the 200-item cap with newest-first ordering, that totals count all items rather than the page, and the empty-state behavior (configured: false).

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 trigger condition before the mechanics, and every clause carries information. The second sentence is long and packs score composition, breakdowns, caps, and empty-state into one run, which costs some scannability.

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-shape explanation isn't required, yet the description still summarizes the payload (health score, coverage states, freshness buckets, lost/new pages). Combined with the empty-state and sibling routing, an agent has everything needed to select and invoke it 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 0%, so the description must carry the load. It fully specifies 'days' (default 30, max 90) and conveys 'siteUrl' as 'a property' with a no-tracker empty-state, though it never states the expected URL format (full URL vs sc-domain) that the minLength-only schema leaves ambiguous.

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: an indexing-health report for a property's tracked URLs over the last N days. It explicitly scopes to tracker URLs only and distinguishes itself from the per-URL sibling (list_tracked_urls) and implicitly from get_indexing_tracker.

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 how indexing of their tracked URLs is trending, including lost or newly indexed pages') and names the alternative for the other case ('Not for the per-URL list: use list_tracked_urls'). It also tells the agent what to do when no tracker exists (configured: false, then add_tracked_urls).

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?