Skip to main content
Glama

sitemap_urls

Discover and parse sitemap.xml files, including sitemap indexes, to extract and list URLs for a domain.

Instructions

Discover and parse sitemap.xml (including sitemap indexes) to list 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": {
      "domain": "<domain>"
    },
    "name": "sitemap_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It mentions sitemap-index handling, which is genuinely useful, but says nothing about network access, robots restrictions, failure modes when no sitemap exists, or how results are capped.

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 no filler. It is efficient, though brevity is partly achieved by omitting information the agent needs.

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?

A simple two-parameter tool, but with zero annotation coverage, no output schema, and undocumented parameters, the description should say more about the domain input, result limits, and what listing behavior to expect.

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%, so the description must compensate and it does not. Neither 'domain' (bare host vs full URL) nor 'limit' (default 500, behavior when exceeded) is explained; only the sitemap.xml context weakly implies the domain parameter's meaning.

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: 'Discover and parse sitemap.xml ... to list URLs', and even notes the sitemap-index case. It does not distinguish itself from sibling URL-listing tools such as commoncrawl_urls or wayback_urls, so an agent must infer the choice.

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 or when-not-to-use guidance and no mention of alternatives. The agent gets no help deciding between this and the other URL-enumeration siblings.

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