Google Search Console by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

gsc monitor indexation freshness

gsc_monitor_indexation_freshness

Read-onlyIdempotent

Monitor Search Analytics freshness and sitemap indexation totals, with an optional URL Inspection sample, to spot delayed data or indexing problems.

Instructions

Read-only monitoring snapshot for Search Analytics freshness, sitemap indexation totals, and an optional small URL Inspection sample.

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.
`inspectUrls`	No	Optional URLs to inspect. Maximum 10 to protect URL Inspection quota.
`searchTypes`	No	Search surfaces to compare. Each surface is queried separately; do not sum overlapping surfaces.
`languageCode`	No	Optional IETF language tag for URL Inspection, e.g. en-US or fr-FR.
`lookbackDays`	No	Recent days to scan for Search Analytics freshness.
`freshnessLagWarningDays`	No	Maximum acceptable lag in days before freshness is marked delayed/stale.

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, and non-destructive behavior, so the description does not need to restate safety. It adds some context by calling the URL Inspection portion optional and 'small', matching the schema's quota-protection limit, but it does not explain operational behavior such as how the three data sources are combined or whether failures in one section affect the snapshot.

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?

The description is a single front-loaded sentence with no filler. It efficiently lists the three main outputs an agent gets from the call.

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 six optional parameters, rich schema descriptions, annotations, and an output schema, so much of the required context is carried by structured fields. However, for a composite monitoring tool surrounded by more specific siblings, the description should do more to explain why an agent would use this snapshot instead of calling the individual data-freshness, sitemap, and URL-inspection tools.

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 six parameters are already well documented in the input schema. The description adds only the notion of an optional small inspection sample, which lightly reinforces inspectUrls but does not add meaning beyond the schema for siteUrl, searchTypes, lookbackDays, languageCode, or freshnessLagWarningDays.

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 names a specific composite resource: a monitoring snapshot covering Search Analytics freshness, sitemap indexation totals, and an optional URL Inspection sample. That is clear enough to distinguish it from generic tools, but it does not explicitly contrast itself with siblings such as gsc_get_data_freshness, gsc_list_sitemaps, or gsc_inspect_url.

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?

The phrase 'monitoring snapshot' implies a monitoring use case, but there is no explicit guidance on when to choose this tool over the many sibling tools that cover its individual components. No prerequisites, exclusions, or alternatives are stated.

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