Google Search Console by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

gsc get sitemap health

gsc_get_sitemap_health

Read-onlyIdempotent

Retrieve a read-only sitemap health summary including status totals, submitted and indexed counts, warnings, and errors to diagnose sitemap problems.

Instructions

Return an enriched read-only sitemap health summary with status totals, submitted/indexed content counts, warnings, and errors.

Input Schema

Name	Required	Description	Default
`siteUrl`	No	Search Console property URL, e.g. https://example.com/ or sc-domain:example.com. Uses GSC_SITE_URL when omitted.

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv2.0.1Sep 23, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so the safety profile is fully covered. The description adds that the result is an aggregate 'enriched' summary with status totals and warnings/errors, which is useful context, but it does not state anything about freshness/caching, rate limits, or what happens when no sitemap exists.

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?

A single, front-loaded sentence with no filler. The payload contents are listed compactly and nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has one optional, fully documented parameter, rich annotations, and an output schema, so the description does not need to explain return values. The missing piece for a 19-sibling toolset is routing context: why choose this over the other sitemap tools, which the description leaves unaddressed.

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 100%: siteUrl is documented in the schema with an example format and the GSC_SITE_URL fallback. The description adds nothing about siteUrl, so the baseline 3 for high-coverage schemas applies.

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?

States a specific verb and resource ('Return an enriched read-only sitemap health summary') and enumerates the payload contents (status totals, submitted/indexed counts, warnings, errors), so the agent knows exactly what it gets. It does not, however, distinguish itself from sitemap siblings such as gsc_list_sitemaps, gsc_get_sitemap, or gsc_track_sitemap_deltas.

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

Usage Guidelines2/5

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

There is no guidance on when to call this instead of gsc_list_sitemaps, gsc_get_sitemap, or gsc_track_sitemap_deltas, despite four sitemap-related siblings. The agent must infer the choice from the description's mention of 'health summary' and 'totals' alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.