Skip to main content
Glama

sitemap_urls

Extract URLs from a sitemap or sitemap index, including child and .gz sitemaps, then optionally filter by substring and cap results for targeted URL lists.

Instructions

sitemap.xml URL extractor: reads a sitemap or sitemap index (incl. .gz) and up to 10 child sitemaps, returns URLs with lastmod/changefreq/priority, optional substring filter, capped list (up to 5000). Costs 0.002 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesSitemap URL or site origin
limitNo1-5000, default 500
containsNoOnly URLs containing this text
max_childrenNo0-10, default 5

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the child-sitemap traversal limit, the output cap, the per-call price on Base, the x402 payment mechanism, and the exact failure mode without a key. It does not state whether nested indexes are followed beyond one child level or whether the response signals truncation at 5000.

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 with no filler: capability and limits first, cost and auth prerequisite second. Every clause carries information an agent needs before calling.

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 names the returned fields and their richness, and it covers cost and auth. Remaining gaps are around truncation signaling and multi-level sitemap recursion depth, which an agent would want to know but which are secondary for a scraping-style extractor.

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%, so the schema already documents all four parameters, and the baseline is 3. The description reinforces the substring filter and the 5000/10 bounds but adds no syntax or format detail beyond the schema, and it does not resolve the oddity that limit/max_children are typed as strings in the schema.

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?

States a specific verb and resource ('sitemap.xml URL extractor: reads a sitemap or sitemap index') and adds the scope details that matter: .gz support, up to 10 child sitemaps, and returned fields (lastmod/changefreq/priority). No sibling in the list does anything similar, so an agent can route to it unambiguously.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operating context — optional substring filtering, a hard 5000-URL cap, and the prerequisite of a payment key with the 402 challenge as the failure path. It stops short of explicit when-to-use/when-not guidance relative to alternatives, but the task is narrow enough that this is minor.

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