Skip to main content
Glama

MetricPort

Sitemaps

gsc_sitemaps
Read-onlyIdempotent

Submitted sitemaps with status, errors, warnings and URL counts.

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": {
      "property": "<property>"
    },
    "name": "gsc_sitemaps"
  }
}

Input Schema

NameRequiredDescriptionDefault
propertyYesSearch Console property id from list_properties, e.g. sc-domain:example.com or https://www.example.com/

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful return-shape information (status, errors, warnings, URL counts), which matters since there is no output schema, but it omits pagination, sitemap URL listing, and any auth/scope detail.

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 tight sentence with no filler. It is efficient, though it is a noun phrase fragment rather than a complete action statement, which slightly limits front-loading of intent.

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 simple one-parameter read tool with no output schema, the description conveys the returned fields, which is the key missing piece. However, it omits any usage context or verb, leaving the agent to infer that this is a passive retrieval of sitemap diagnostics.

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% for the single property parameter, and the schema already explains its format and source (list_properties). The description adds nothing about the parameter, so the baseline of 3 is appropriate.

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 names the specific resource (submitted sitemaps) and enumerates the data returned (status, errors, warnings, URL counts), so an agent knows exactly what this tool yields. It lacks an explicit verb like 'Retrieve', but as the only sitemap-related tool among the siblings there is no ambiguity about what it does.

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 mention of prerequisites, and no alternatives named. The only routing hint (fetching the property id from list_properties) lives in the schema, not the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.