Skip to main content
Glama
@mgcrea/mcp-google-search-console

@mgcrea/mcp-google-search-console

by mgcrea

Search Console: List Sitemaps

gsc_list_sitemaps
Read-only

Lists sitemaps submitted for a Search Console property, or child sitemaps inside a sitemap index, with submission status, warnings, errors, and submitted URL counts.

Instructions

The sitemaps submitted for a property (or, with sitemap_index, the child sitemaps listed in that index): path, type, last submitted and last downloaded times, whether processing is pending, warning and error counts, and submitted URL counts per content type. Google no longer reports an indexed count here — use gsc_inspect_url for a page's index status.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>"
    },
    "name": "gsc_list_sitemaps"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe Search Console property, e.g. "sc-domain:example.com" (a domain property: every protocol and subdomain) or "https://www.example.com/" (a URL-prefix property: exactly that scheme, host and path). A bare "example.com" or a URL without its trailing slash is resolved against the properties this account can see, preferring the domain property; the response's `site` says which property was read. gsc_list_sites lists them.
sitemap_indexNoA sitemap index URL, e.g. "https://www.example.com/sitemap_index.xml", to list the sitemaps inside it instead of the submitted ones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The readOnlyHint and openWorldHint annotations already establish the safety profile, and the description adds substantive behavioral detail: the exact return fields, the sitemap-index variant, and the important limitation that indexed counts are no longer reported. It does not disclose pagination or authentication details, but it adds meaningful context beyond the 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?

Two dense sentences, front-loaded with the primary purpose and immediately followed by the return fields and the alternative for indexed counts. No sentence is redundant or wasted.

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?

With only two parameters, full schema coverage, and no output schema, the description does the necessary work of enumerating return values and flagging a missing metric that could otherwise confuse the agent. It is complete for a read-only listing 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?

Schema description coverage is 100%, so both parameters are already well documented in the schema. The description adds only a brief parenthetical clarifying that sitemap_index switches the listing to child sitemaps inside an index; otherwise the schema carries the parameter semantics.

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 states a specific verb and resource: listing the sitemaps submitted for a property, or child sitemaps when sitemap_index is supplied. It enumerates exactly what is returned and explicitly contrasts its scope with gsc_inspect_url for index status, so an agent can distinguish its core purpose.

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?

It gives clear context for using this tool to enumerate submitted sitemaps and explicitly redirects index-status questions to gsc_inspect_url. It does not mention gsc_get_sitemap or other alternatives, so it stops short of full when-to-use versus when-not-to-use guidance.

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