Skip to main content
Glama

DomainVet

List a site's URLs from its sitemaps

sitemap_urls
Read-onlyIdempotent

Find a site's XML sitemaps (robots.txt Sitemap lines, /sitemap.xml, /sitemap_index.xml), follow sitemap indexes, and return the page URLs listed. Use it to enumerate a site's pages before reading them.

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
urlYesSite URL or direct sitemap.xml URL
limitNoMax URLs to return (default 500, max 5000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint) and open-world access, so the description earns credit for the extra behavioral detail it does provide: the multi-source discovery strategy and that sitemap indexes are followed recursively. It does not say what happens when a site has no sitemap or how failures are surfaced, which keeps it below 5.

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 sentence carrying purpose, mechanism, and return value, followed by a single sentence of usage guidance. Front-loaded, no redundancy, nothing wasted.

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?

For a two-parameter read-only tool with a rich schema and full annotation coverage, the description supplies the return value (page URLs) and the discovery behavior an agent needs. The only gap is the no-sitemap/failure case, which is minor given annotations already signal open-world network access.

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% and already documents both parameters, including the site-URL-or-sitemap-URL duality and the 500 default / 5000 cap. The description adds no syntax or format meaning beyond that, so the baseline 3 applies.

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 chain (find, follow, return) and the exact resource (XML sitemaps and the page URLs listed), plus the discovery locations (robots.txt Sitemap lines, /sitemap.xml, /sitemap_index.xml). Nothing about this could be confused with the sibling tools dns_lookup, rdap_domain, or ssl_certs.

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 an explicit use case: enumerate a site's pages before reading them, which tells the agent where this fits in a workflow. It stops short of naming when-not-to-use or a specific alternative tool, so it gets a 4 rather than a 5.

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