Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Search Console: List sitemaps

google_search_console_list_sitemaps
Read-only

Lists sitemaps submitted for a Search Console property, including status, last processed date, errors, and warnings to help diagnose indexing issues.

Instructions

[UNIFIED] List sitemaps submitted for a Search Console property, including their submission status, last processed date, errors, and warnings. Use list_properties first to discover available property URLs.

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

Input Schema

NameRequiredDescriptionDefault
siteYes
site_urlYes
page_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes this as a non-mutating read, so the description only needs to add context. It adds the shape of the returned data (status, dates, errors, warnings) but says nothing about result limits, pagination behavior, or how empty sitemap lists appear.

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 sentences with no filler, front-loading the resource and result fields before the ordering prerequisite. Every clause earns its place.

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?

With no output schema the description sensibly names the returned fields, and readOnlyHint covers the safety profile. However, with 0% schema coverage on a three-parameter tool, the undefined site vs. site_url relationship and undocumented pagination leave the definition short of what an agent needs to call it reliably.

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

Parameters2/5

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

Schema description coverage is 0% for three parameters, so the description must carry the burden and it does not. It never explains the distinction between the two required parameters `site` and `site_url`, nor the purpose of `page_token` for pagination, leaving an agent to guess at potentially overlapping identifier fields.

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?

States a specific verb and resource ("List sitemaps"), scopes it to "submitted for a Search Console property," and enumerates what is returned (submission status, last processed date, errors, warnings). It is clearly not the property-listing tool, but it does not explicitly contrast itself with any sibling beyond the prerequisite mention.

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?

Gives an actionable prerequisite: "Use list_properties first to discover available property URLs," which tells the agent what to call before this tool. It offers no when-not-to-use guidance or alternatives, but for a narrow list operation the context is adequate.

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