Skip to main content
Glama
modelbrain-search-console

modelbrain-search-console

Official

List sitemaps

list_sitemaps
Read-onlyIdempotent

Retrieve sitemaps submitted for a Search Console property and see when Google last read them, plus errors, warnings, and URL counts.

Instructions

Sitemaps submitted for a property, with when Google last read them, errors, warnings and how many URLs each holds.

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_urlYesThe Search Console property, for example sc-domain:example.com or https://example.com/. A plain domain or page URL also works: it is matched to the right property.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description usefully discloses what comes back (last-read timestamps, error/warning counts, URL totals) in the absence of an output schema, but says nothing about permission requirements, empty/unsubmitted-property behavior, or result size.

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?

A single front-loaded sentence with zero filler; the returned-field list is packed efficiently. It is a noun-phrase fragment rather than a full statement of action, which slightly weakens the lead.

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?

The return-value gap is closed since no output schema exists, and the single parameter is fully documented in the schema. However, a read tool for a verified-property API should at least signal that the property must be accessible and what an empty sitemap list means.

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?

With one parameter at 100% schema description coverage, the schema already explains site_url formats and property matching. The description adds no extra meaning about the parameter, so the baseline 3 applies.

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?

"Sitemaps submitted for a property" names a specific resource and scope, and the trailing clause enumerates the payload (last read time, errors, warnings, URL counts). It is clearly distinct from list_sites, inspect_url, and search_performance, though it never explicitly contrasts itself with 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?

There is no when-to-use guidance, no prerequisites (e.g. property verification), and no named alternative. The agent must infer from the field list that this is for auditing sitemap health rather than inspecting individual URLs.

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