Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_api_sitemap_crawler

Parse a sitemap or site URL into a URL list, with an optional limit, to support crawling, auditing, and indexing workflows.

Instructions

[Web Intelligence] Parse a sitemap into a URL list Measured p50 12 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://api.caelaralabs.com.

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": "caelara_api_sitemap_crawler"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesSitemap or site URL
limitNoMax URLs (default 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden. It discloses latency benchmarks and the backing endpoint, but says nothing about error handling, rate limits, whether sitemap indexes are followed, or what happens on malformed input.

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?

Very short and front-loaded with the core purpose. The benchmark parenthetical and endpoint host are marginally useful provenance but consume a large share of an already tiny description.

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?

For a simple two-parameter fetch tool with no output schema, the description does state the return shape (a URL list). It is still thin on limits behavior, failure modes, and sitemap edge cases that would matter in practice.

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 both parameters are already documented in the schema, and the description adds no further meaning about the url parameter (accepts site or sitemap URL) or the limit default/truncation behavior. Baseline 3 applies.

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 into a URL list,' which tells an agent exactly what comes out. It does not explicitly contrast with near-neighbors such as the URL-to-markdown or SEO x-ray tools, so it falls short of full sibling differentiation.

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 guidance on when to choose this tool over alternatives, no prerequisites, and no exclusions (e.g., whether robots.txt or sitemap index files are handled). Usage is only inferable from the one-line purpose.

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

Deploy Server

Other Tools