Skip to main content
Glama

crawl_sitemap

Crawl a website's pages listed in its sitemap.xml. Auto-discovers sitemaps from robots.txt or /sitemap.xml and supports URL filtering for targeted extraction.

Instructions

Crawl a website using its sitemap.xml. Auto-discovers sitemaps from robots.txt or /sitemap.xml. Supports sitemap index files and URL filtering.

When to use: Extracting content from many pages of a site that publishes a sitemap.xml. When NOT to use: Use crawl for BFS discovery when no sitemap exists, or navigate for a single page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesWebsite URL (auto-discovers /sitemap.xml, /sitemap_index.xml)
sitemap_urlNoExplicit sitemap URL (skips auto-discovery)
filterNoURL glob pattern to filter which sitemap URLs to visit
max_pagesNoMaximum number of pages to visit. Default: 50
output_formatNoContent format per page. "markdown-clean" uses cheerio+turndown to strip nav/footer/ads. Default: markdown
onlyMainContentNomarkdown-clean only: strip nav/header/footer/aside/ads. Default: true.
includeLinksNomarkdown-clean only: preserve <a> as markdown links. Default: true.
queryNomarkdown-clean content_filter="bm25" query terms.
content_filterNomarkdown-clean only: deterministic fit_markdown filter. Default: none.
return_rawNomarkdown-clean only: include raw_markdown in each page. Default: false.
return_fitNomarkdown-clean only: include fit_markdown and use it as content when filtering. Default: true when filtered.
concurrencyNoMax concurrent page fetches. Default: 3
engineNoFetch engine: "cdp" (default, opens a Chrome tab per page), "static" (Node fetch only, fails closed on insufficient pages), or "auto" (static first, fall back to CDP when static is insufficient).
cache_modeNoOpt-in crawl content cache mode. Default: disabled.
cache_ttl_msNoMaximum age for enabled/read_only cache hits. Omit for no TTL expiry.
cache_scopeNoCache namespace/safety scope. Default: public.
include_metricsNoWhen true, include approximate output size/token metrics in the JSON result. Default: false.
Behavior4/5

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

Annotations provide readOnlyHint=false and others; description adds context on auto-discovery, caching modes, and filtering. No contradictions, but could disclose more about side effects or state changes.

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?

Concise and well-structured with front-loaded purpose and clear usage section. Every sentence adds value; no fluff.

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?

Covers usage, behavior, and parameters well. Minor gap: no mention of output format or return structure, but implied by 'extracting content' and parameter descriptions.

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% with detailed parameter descriptions. The description adds overview but no additional insight beyond what the schema already provides, meeting baseline for high coverage.

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?

The description clearly states it crawls a website using sitemap.xml, with auto-discovery and URL filtering. It distinguishes from siblings by contrasting with 'crawl' and 'navigate' in the usage guidelines.

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

Usage Guidelines5/5

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

Explicitly states when to use (many pages with sitemap) and when not to use (no sitemap -> crawl, single page -> navigate), providing clear alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shaun0927/openchrome'

If you have feedback or need assistance with the MCP directory API, please join our Discord server