Skip to main content
Glama

crawl

Discover URLs from a starting page and scrape each one, enabling bulk extraction of entire site sections or documentation.

Instructions

Multi-page crawl: discover URLs on root, then scrape each.

Use this when the user wants to crawl an entire site section or docs, or needs multiple pages scraped in bulk. For single pages use scrape; for research questions use deep_research.

Args: root: start URL. max_pages: hard cap on pages scraped. css_selector: scope each page's html/markdown to the matched element (non-llm: lxml re-scope of the fetched HTML; llm: native crawl4ai css_selector). prefer: "auto" | "fast" | "stealth" | "llm" (llm = Crawl4AI BFS deep-crawl). include_paths: regex — keep only URLs matching (matched against full URL). exclude_paths: regex — drop URLs matching (e.g. /tag/|/page/\d+). max_depth: 0 = flat harvest from the root page's links (default); >0 = true BFS up to that link depth, honoring the filters.

Returns: {root, pages: [{url, markdown, title, ...}], count, discovered, elapsed_ms} or {error, root} on failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootYes
preferNoauto
max_depthNo
max_pagesNo
css_selectorNo
exclude_pathsNo
include_pathsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden, and it delivers: it explains the discover-then-scrape flow, flat vs BFS depth behavior, filtering by regex, the `prefer` mode variants, and the exact success/error return shapes. This goes well beyond a minimal statement of what the tool does.

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?

The description is well-structured and front-loaded: a crisp one-sentence summary, then usage guidance, then a tight Args block, then the Returns shape. Every line adds information without padding, which is appropriate for a 7-parameter tool with no schema-level parameter descriptions.

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

Completeness5/5

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

Given no annotations, an output schema present, and seven parameters, the description is operationally self-sufficient. It covers purpose, when to use it, alternatives, all parameter semantics, the crawling algorithm variants, filters, and the return contract including the error case.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for every parameter, and it does. All seven arguments are meaningfully explained, including the regex semantics for include/exclude paths, the meaning of max_depth, and the `prefer` option values.

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 opens with a specific, action-oriented definition: 'Multi-page crawl: discover URLs on root, then scrape each.' It also distinguishes itself from siblings by naming `scrape` for single pages and `deep_research` for research questions.

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?

The description clearly says when to use crawl (entire site section, docs, bulk multi-page needs) and gives explicit alternatives for single pages and research questions. However, it does not distinguish crawl from the `batch_scrape` sibling, and its phrase 'multiple pages scraped in bulk' could overlap with that tool, so the routing guidance is not fully exhaustive.

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