Skip to main content
Glama
AminForou

Google Search Console MCP

manage_sitemaps

}```json {

Instructions

All-in-one tool to manage sitemaps (list, get details, submit, delete).

Args:
    site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or
              "sc-domain:example.com"). Domain properties cover all subdomains — use the
              domain property as site_url and filter by page to analyze a specific subdomain.
    action: The action to perform (list, details, submit, delete)
    sitemap_url: The full URL of the sitemap (required for details, submit, delete)
    sitemap_index: Optional sitemap index URL for listing child sitemaps (only used with 'list' action)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_urlYes
actionYes
sitemap_urlNo
sitemap_indexNo
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'delete' and 'submit' actions but does not disclose if these are destructive, idempotent, what permissions they require, or what error conditions to expect. The behavioral traits remain largely undocumented.

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 appropriately structured with a summary sentence followed by an Args section. The information is dense but necessary given the 0% schema coverage. The site_url explanation is lengthy but contains essential domain-specific details; no sentences appear wasteful.

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

Completeness3/5

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

For a tool with four distinct operational modes and no output schema, the description adequately covers input parameters but leaves gaps regarding return values, error handling, and the critical decision logic for selecting this tool over its specialized siblings. It meets minimum viability but has clear gaps.

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

Parameters5/5

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

Given 0% schema description coverage, the Args section provides critical compensation: it explains the exact format for `site_url` (including domain property syntax), lists valid values for `action`, and clarifies conditional requirements for `sitemap_url` (required only for certain actions) and `sitemap_index`. It adds significant semantic value beyond the bare schema.

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 clearly states it is an 'All-in-one tool to manage sitemaps' and enumerates the four supported actions (list, get details, submit, delete). However, it fails to distinguish this consolidated tool from specific siblings like `submit_sitemap`, `delete_sitemap`, and `get_sitemaps`, leaving the agent without criteria to choose between them.

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?

While it mentions that `site_url` must come from `list_properties`, it provides no guidance on when to use this multi-action tool versus the specialized sibling tools that perform the same individual actions. The agent is left to guess whether to use this 'all-in-one' tool or the specific atomic tools.

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/AminForou/mcp-gsc'

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