Skip to main content
Glama
Sign In
gsc-mcp

gsc-mcp

by ajmalaksar25
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List sitemaps

list_sitemaps

Retrieve all submitted sitemaps for a property, including processing status and error/warning counts, to monitor indexing health.

Instructions

List all sitemaps submitted for a property, with processing status and error/warning counts.

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": "list_sitemaps"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteUrlNoProperty as shown in Search Console: a URL-prefix property ends with a slash (e.g. "https://example.com/") or a domain property uses "sc-domain:example.com". May be a registered alias, or omitted to use the active/default site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description carries burden. It discloses output includes status and counts, but does not mention read-only nature, authentication, or rate limits. Acceptable for a query tool.

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?

Single sentence with no wasted words. Front-loaded with verb and resource, then adds specific details about output. Highly concise.

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?

For a simple list tool with one optional param and no output schema, the description is fairly complete. Covers what is listed and for what resource. Minor lack of detail on return format or pagination, but sufficient.

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 covers the single optional parameter siteUrl with 100% description. Tool description adds no additional meaning beyond what schema already provides. Baseline 3 is appropriate.

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?

Description clearly states the tool lists all sitemaps for a property, including status and counts. Distinguishes from sibling tools like get_sitemap which likely retrieves a single sitemap.

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

Usage Guidelines3/5

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

Implied usage is to get an overview of all sitemaps, but description does not explicitly state when to use this vs alternatives like get_sitemap, nor provide exclusions or prerequisites.

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