Skip to main content
Glama
Sign In
Google Search Console MCP

Google Search Console MCP

by rohoswagger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List sitemaps

gsc_list_sitemaps

List submitted sitemaps for any Google Search Console property to verify indexing status and identify missing or invalid sitemaps.

Instructions

List submitted sitemaps for a Search Console property.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
siteUrlNo
allSitesNo
siteUrlsNo
sitemapIndexNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does communicate that this is a read-only listing of 'submitted' sitemaps rather than all discovered sitemaps, which is useful. However, it does not disclose output format, pagination, property URL requirements, or any side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single focused sentence with no filler or repetition. It is concise and front-loaded, though the brevity comes at the cost of missing important behavioral and parameter context.

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

Completeness2/5

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

Given four undocumented parameters, zero schema description coverage, no annotations, and no output schema, this description is too sparse to fully support correct invocation. An agent would be left guessing about property selection and behavior across multiple sites.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description adds no parameter-level meaning. siteUrl, allSites, siteUrls, and sitemapIndex are not explained at all, leaving an agent unable to know how to request a single property versus multiple sites or how sitemapIndex is used.

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 states a clear verb ('List'), a specific resource ('submitted sitemaps'), and a scope ('for a Search Console property'). It is understandable and distinct from sibling list_sites, though it does not explicitly contrast with gsc_get_sitemap.

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 description gives no guidance on when to use this tool versus alternatives like gsc_get_sitemap or gsc_submit_sitemap. There are no exclusions, prerequisites, or context clues to help an agent choose between closely related sitemap operations.

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

Deploy Server

Other Tools