Skip to main content
Glama

search_console_sitemaps_list

List all sitemaps registered in Search Console for a property, including their crawl status and submission details. Returns raw Webmasters sitemap data.

Instructions

List every sitemap registered against a Search Console property, with their most recent crawl status. Returns the raw Webmasters 'sitemap' array: [{path (absolute sitemap URL), lastSubmitted (ISO 8601), isPending, isSitemapsIndex, type ('sitemap'|'sitemapIndex'|'rssFeed'|'atomFeed'|'urlList'|'patternSitemap'), lastDownloaded (ISO 8601), warnings (int), errors (int), contents: [{type, submitted (int), indexed (int)}]}]. Read-only. For submitting or resubmitting a sitemap use search_console_sitemaps_submit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_urlYesProperty identifier as registered in Search Console. For URL-prefix properties use the full URL including trailing slash (e.g. 'https://example.com/'). For Domain properties use the 'sc-domain:' prefix (e.g. 'sc-domain:example.com'). The property must be verified and accessible to the authenticated Google account.
Behavior5/5

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

Despite no annotations, the description states 'Read-only' and fully details the return structure, including field names and types, ensuring transparency.

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, well-structured paragraph with no redundancy, front-loads the action, and provides essential details efficiently.

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

Completeness5/5

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

Given the simplicity of the tool (one parameter, no output schema), the description covers all necessary aspects: purpose, return format, read-only nature, and alternative tool.

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?

The single parameter is fully described in the input schema (100% coverage), so the description adds no additional meaning beyond the schema.

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 explicitly states the tool lists every sitemap for a Search Console property with crawl status, distinguishing it from the sibling search_console_sitemaps_submit.

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

Usage Guidelines5/5

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

It clearly specifies when to use this tool (for listing) and when not to (for submitting, directing to the sibling tool), providing explicit guidance.

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/logly/mureo'

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