Google Search Console by Get MCP Ads

by get-mcp-ads

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

gsc monitor indexation freshness

gsc_monitor_indexation_freshness

Read-onlyIdempotent

Monitor Search Analytics freshness and sitemap indexation totals; optionally inspect URLs to detect indexing delays.

Instructions

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

Input Schema

TableJSON 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

TableJSON 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.

First observedv2.0.1Sep 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value by clarifying the combined read-only scope and the optional sampling behavior, but it does not disclose details like multiple API calls, quota impact beyond the schema's maxItems note, or operational caveats. No contradiction with annotations.

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 tight sentence that names all three monitoring components and the read-only nature. Every element earns its place, with no filler or repetition.

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?

Given the rich annotations, 100% schema coverage, zero required parameters, and an output schema, the description is nearly complete for a low-complexity tool. The main gap is the absence of when-to-use guidance relative to its many siblings, but that is partly mitigated by the clear composite scope.

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 the input schema fully documents all six parameters. The description itself adds no parameter-specific meaning, but with full schema coverage the baseline of 3 is appropriate.

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 specifies a clear composite purpose: a read-only monitoring snapshot covering Search Analytics freshness, sitemap indexation totals, and an optional URL Inspection sample. It distinguishes the tool from more specific siblings like gsc_query_search_analytics or gsc_get_sitemap, though it does not explicitly name those alternatives.

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?

No guidance is provided on when to use this snapshot tool versus its many siblings. The description does not state scenarios, prerequisites, or exclusions, and the presence of 19 sibling tools makes this omission significant.

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