Skip to main content
Glama
Sign In
ga4-mcp

ga4-mcp

by chimpmatic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

gsc_list_sitemaps

List all sitemaps submitted for a site in Google Search Console. Provide the site URL to retrieve the sitemap list.

Instructions

Lists all sitemaps submitted for a site in Google Search Console.

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": "gsc_list_sitemaps"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_urlYesSite URL as defined in GSC (e.g. "https://example.com/" or "sc-domain:example.com")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior2/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 only states what the tool does, but omits details like read-only nature, authentication needs, rate limits, error handling (e.g., if site not in GSC), or output format.

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 a single, clear sentence with no unnecessary words. It is front-loaded and efficient.

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

Completeness2/5

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

Given no output schema and no annotations, the description lacks completeness. It does not describe the return format (e.g., list of sitemap URLs and statuses) or how to interpret results. Sibling tools are not differentiated, and the simple operation still benefits from behavioral context.

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 coverage is 100% (site_url clearly described). The description does not add meaning beyond the schema, but the baseline is 3 given high coverage. No extra parameter elaboration.

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's function: listing all sitemaps for a site in GSC. It uses a specific verb ('lists') and resource ('sitemaps submitted for a site'), and distinguishes from sibling tools like gsc_submit_sitemap and gsc_list_sites.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., gsc_submit_sitemap or gsc_search_analytics). It does not mention prerequisites like site verification or context such as needing to list sitemaps before submitting.

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