Skip to main content
Glama
Sign In
searchconsole-mcp

searchconsole-mcp

by harisnadeem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_sitemaps

Retrieve all submitted sitemaps for a website, including feedpath, type, and content counts.

Instructions

List all sitemaps submitted for a website.

Args: site_url: The site whose sitemaps to list, e.g. 'https://example.com/'.

Returns: Dictionary with 'sitemap' list containing feedpath, type, contentsCounts, etc.

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_url": "<site_url>"
    },
    "name": "list_sitemaps"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns a dictionary with specific fields, suggesting a read operation, but does not explicitly state that it is non-destructive or address potential 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.

Conciseness5/5

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

The description is extremely concise, consisting of three sentences. The first sentence front-loads the purpose, and the third sentence explains the return value without unnecessary words.

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 tool's simplicity (single parameter, no output schema), the description covers the essential aspects: what it does and the general shape of the return. It does not elaborate on every return field, but this is acceptable without an 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 input schema has only one required parameter (site_url) with 0% schema description coverage. The description adds value by providing an example format ('https://example.com/'), which clarifies the expected structure 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 clearly states the tool lists all sitemaps for a website. The verb 'list' and resource 'sitemaps' are specific, and it distinguishes from siblings like delete_sitemap, get_sitemap, and submit_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?

The description implies usage by stating it lists sitemaps for a website, but it does not explicitly indicate when to use this tool versus alternatives like get_sitemap or submit_sitemap, nor does it provide any context on when not to use it.

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