Skip to main content
Glama

Get every URL a website lists in its XML sitemaps

sitemap
Read-only

Get every URL a website lists in its XML sitemaps: finds sitemaps via robots.txt and common paths, follows sitemap indexes (up to 5 children) and returns URLs with lastmod dates. Optional limit (default 1000, max 5000). Takes 1-6 s. Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.003 per call (x402, USDC on Base).

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": {
      "url": "<url>"
    },
    "name": "sitemap"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
limitNoMax URLs returned (1-5000, default 1000)
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only cover readOnlyHint and openWorldHint, and the description goes well beyond them: sitemap index recursion capped at 5 children, lastmod values in the output, a 1-6 s latency estimate, a free tier of 20 calls/day, and a metered $0.003/call x402 USDC-on-Base price. Cost and latency disclosure are exactly the behavioral context an agent needs before calling a network tool.

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?

Front-loaded with the core behavior, then mechanism, limits, timing, and pricing in a compact sequence with no filler. Minor redundancy in repeating the limit default and cap that the schema already states, and the pricing sentences are dense but each carries decision-relevant information.

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 correctly specifies the return shape (URLs plus lastmod dates), depth limits, and the payment flow entry point ('omit on the first call to get the price'). It stops short of covering failure cases such as a site with no sitemap or partial sitemap failures, and whether results are deduplicated.

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%, so url, limit, and payment are already documented in the schema, and the description's restatement of the default 1000 / max 5000 adds nothing new. It only indirectly illuminates the payment parameter by explaining the pricing model that triggers it.

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 ('Get every URL a website lists in its XML sitemaps') and even names the discovery mechanism (robots.txt plus common paths). It does not explicitly contrast with adjacent siblings such as links, key_pages, or robots, so the differentiation is implicit rather than stated.

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 by the description's scope — reach for this when you want the full published URL inventory of a site rather than links found on a rendered page. However, there is no explicit when-to-use/when-not guidance or named alternative, leaving selection between this and siblings to inference.

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.