Skip to main content
Glama
shutovdef-dotcom

Google Search Console MCP Server

audit_sitemap_urls

Safely fetch and parse XML sitemaps for read-only diagnostics, validating the URL against your Google Search Console property and blocking unsafe targets.

Instructions

Safely fetch and parse an XML sitemap or sitemap index for read-only diagnostics.

This tool does not submit/delete sitemaps and does not call URL Inspection. It
validates the sitemap URL against the supplied GSC property scope before any
network request, resolves DNS to block unsafe IP targets, disables redirects,
and caps response bytes.

Args:
    site_url: Exact GSC property URL from list_properties, or sc-domain:example.com
    sitemap_url: Full URL of the sitemap XML to fetch
    max_urls: Maximum number of URL or child sitemap entries to include in samples

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_urlsNo
site_urlYes
sitemap_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses safety measures (validation, DNS resolution, redirect disabling, byte capping) and confirms read-only behavior. Could mention error handling but overall good.

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 concise and well-structured, with a clear purpose statement followed by safety notes and parameter explanations. Every sentence earns its place.

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 existence of an output schema, the description covers input and safety adequately. It could be more explicit about return data but likely covered by output schema.

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?

The description adds meaning to all three parameters beyond the schema, explaining site_url format, sitemap_url as full URL, and max_urls limit on samples. Schema coverage is 0%, so this is valuable; slight improvement could be format requirements for sitemap_url.

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?

The description clearly states the tool fetches and parses XML sitemaps for read-only diagnostics, using specific verbs and distinguishing from sibling tools like submit_sitemap and delete_sitemap.

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

Usage Guidelines4/5

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

The description explicitly states what the tool does not do (submit/delete sitemaps, call URL Inspection), providing context for when to use versus siblings. However, it could be more explicit about when to use this tool instead of other read tools like get_sitemaps.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shutovdef-dotcom/google-search-console-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server