Skip to main content
Glama

Sitemap Extractor API - all URLs of a website from its sitemaps

sitemap_extractor
Read-onlyIdempotent

Find a site's sitemaps (robots.txt Sitemap: lines, /sitemap.xml, sitemap indexes, .gz, .txt) and return every page URL with lastmod, changefreq and priority, up to 50,000. Filter by a word in the URL. For SEO audits, crawling plans and content monitoring. Live fetch, ~1-5 s. Free: 25 calls/day per IP. Paid: $0.005 per call via x402 at https://radarbg.com/x402/sitemap-extractor.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "radarbg.com",
      "maxItems": 50
    },
    "name": "sitemap_extractor"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoDomain or sitemap URL, e.g. example.com or https://example.com/sitemap.xml
containsNoOnly URLs containing this text, e.g. /blog/
maxItemsNoMax URLs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag readOnly/openWorld/idempotent, and the description layers on genuinely new operational facts: live fetch at ~1-5 s latency, a 25 calls/day per-IP free quota, and paid x402 pricing at $0.005 per call. It also states the 50,000 URL cap and the return fields (lastmod, changefreq, priority), which the annotations cannot convey.

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?

One dense, front-loaded block: what it does, what it returns, the filter, the use cases, then latency/limits/pricing. Every clause carries information an agent would otherwise have to discover by trial; no filler or repetition.

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 carries the return-shape burden ('every page URL with lastmod, changefreq and priority') and discloses cost and rate limits. The one gap is that no parameter is required, yet the description never says what happens if 'url' is omitted.

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?

The schema already documents all three parameters at 100% coverage, including the maxItems minimum/maximum, so the baseline is 3. The description adds only 'Filter by a word in the URL' and the 'up to 50,000' ceiling, which restates schema constraints rather than adding new meaning.

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 ('Find a site's sitemaps... return every page URL') and enumerates the discovery sources (robots.txt Sitemap: lines, /sitemap.xml, indexes, .gz, .txt). No sibling tool covers sitemap enumeration, so an agent can distinguish this from website_report or redirect_checker purely from the text.

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 usage contexts ('For SEO audits, crawling plans and content monitoring') so the agent knows when this fits. It stops short of exclusions or naming an adjacent tool for related-but-different needs, but the purpose is narrow enough that ambiguity is low.

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.

Resources