Skip to main content
Glama

Caelara Labs Web Intelligence

sitemap_crawler

Parse a sitemap into a URL list

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

Input Schema

NameRequiredDescriptionDefault
urlYesSitemap or site URL
limitNoMax URLs (default 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about network fetching, sitemap-index recursion, whether the limit truncates results, or error handling for malformed sitemaps. Only the bare transformation is stated.

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 zero filler, though the terseness leaves little room for the behavioral context an unannotated tool needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (2 parameters, one required, no nested objects, no output schema) and the schema is fully described, so the essentials are covered. However, with no annotations and no output schema, the description should have said something about fetching behavior and return shape beyond "URL list".

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%, with both url ("Sitemap or site URL") and limit ("Max URLs (default 100)") documented inline, so the baseline is 3. The description adds no meaning beyond the schema, notably not clarifying how a plain site URL differs from a sitemap URL.

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 pair ("Parse a sitemap") plus the output ("URL list"), so the operation is unambiguous. It does not differentiate itself from siblings such as url_to_markdown or seo_xray, which might also consume URLs.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. An agent must infer from the title and sibling names that this is the tool for extracting URLs from a sitemap rather than converting or analyzing pages.

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