Skip to main content
Glama
@mgcrea/mcp-google-search-console

@mgcrea/mcp-google-search-console

by mgcrea

Search Console: Get Sitemap

gsc_get_sitemap
Read-only

Retrieve one submitted sitemap’s processing status, including submission and download dates, pending state, index flag, warning and error counts, and submitted URL counts by content type.

Instructions

One submitted sitemap's processing status: last submitted and downloaded, pending, whether it is an index, warning and error counts, and submitted URL counts per content type. A 404 means it was never submitted for this property (gsc_list_sitemaps lists those that were).

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>",
      "sitemap_url": "<sitemap_url>"
    },
    "name": "gsc_get_sitemap"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe Search Console property, e.g. "sc-domain:example.com" (a domain property: every protocol and subdomain) or "https://www.example.com/" (a URL-prefix property: exactly that scheme, host and path). A bare "example.com" or a URL without its trailing slash is resolved against the properties this account can see, preferring the domain property; the response's `site` says which property was read. gsc_list_sites lists them.
sitemap_urlYesFull URL of the sitemap, e.g. "https://www.example.com/sitemap.xml" — the `path` from gsc_list_sitemaps.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely new behavioral context beyond that: a 404 signal means never-submitted rather than an error condition, plus the mix of volatility fields (pending, last downloaded) the caller can expect. It does not cover other failure modes such as permission or invalid-property errors.

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, both front-loaded with the payload description first and the edge-case routing second. Dense but every clause carries information; nothing is restated from the title or schema.

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?

With no output schema, the description effectively serves as one by listing the returned fields, which is exactly what an agent needs for a single-record read. The remaining gap is the absence of other error semantics beyond 404 (auth failures, invalid property), which is minor for a two-parameter read tool.

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 description coverage is 100% and both parameters are fully documented in the schema, including site resolution rules and the sitemap_url pattern, so the baseline is 3. The description adds only indirect parameter guidance by naming gsc_list_sitemaps as the source of the sitemap URL.

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 title supplies the verb (Get) and the description pins the resource precisely: "One submitted sitemap's processing status," then enumerates the returned fields (submission/download timestamps, index flag, warning/error counts, per-type URL counts). It also differentiates from gsc_list_sitemaps by explaining the 404 case. It stops just short of a 5 because the operative verb lives in the title rather than the description.

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?

Usage is implied rather than stated: read status for a sitemap you already know exists, and use gsc_list_sitemaps to discover which ones were submitted. There is no explicit when-to-use or when-not-to-use framing, and no prerequisites (e.g., which property scope is required) are called out.

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