Google Search Console by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

gsc track sitemap deltas

gsc_track_sitemap_deltas

Read-onlyIdempotent

Compare current Google Search Console sitemap snapshots to an agent-provided baseline to detect indexed, submitted, and error count changes. Run read-only delta tracking with no stored state.

Instructions

Read-only sitemap delta tracker. Fetches the current sitemap snapshot and compares it to an agent-provided baseline; no state is written.

Input Schema

Name	Required	Description
`siteUrl`	No	Search Console property URL, e.g. https://example.com/ or sc-domain:example.com. Uses GSC_SITE_URL when omitted.
`baseline`	No	Previous snapshot entries from this tool's snapshot output.
`includeUnchanged`	No	Include entries with no observed change in the comparison.
`minAbsIndexedDelta`	No	Minimum absolute indexed URL delta to include otherwise unchanged sitemaps.

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.

Changed8 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / baseline / items / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / baseline / items / properties / errors / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / baseline / items / properties / indexed / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / baseline / items / properties / submitted / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / baseline / items / properties / warnings / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / minAbsIndexedDelta / maximum
```
Added value: +9007199254740991
```

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

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, but the description still adds meaningful context: the comparison is stateless and depends on an agent-supplied baseline, meaning the server stores nothing between calls. That goes beyond the annotation set and shapes invocation behavior. It stops short of describing the delta output shape, but an output schema 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?

Two sentences, zero waste, with the read-only stateless nature front-loaded before the mechanism. Nothing redundant.

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

Completeness4/5

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

With an output schema, rich annotations, and full schema coverage, the description is nearly sufficient. The one omission an agent might want is the first-run behavior (empty default baseline returns a full snapshot), which is only inferable from the schema default.

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%, so all four parameters (including baseline, includeUnchanged, minAbsIndexedDelta) are already documented. The description only reinforces that the baseline is agent-provided; it adds no syntax or format detail beyond the schema, so baseline 3 is correct.

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 chain (fetch current snapshot, compare to baseline) and a clear resource (sitemap deltas). It's distinguishable from gsc_list_sitemaps and gsc_get_sitemap_health by the comparison framing, though it doesn't name those siblings explicitly.

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

Usage Guidelines3/5

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

'agent-provided baseline' implies this is a repeat-call tool where the prior snapshot output is fed back in, which is useful implied usage. However, it never says when to pick this over gsc_get_sitemap_health or gsc_list_sitemaps, nor what happens on a first call with no baseline.

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