mcp-cloudflare-crawl

crawl_and_wait

Crawl a website and wait for completion, returning final results in one call. Best for small crawls, combining start and status polling to avoid managing job states.

Instructions

Start a crawl and wait for it to complete, returning the final results.

This is a convenience tool that combines crawl_start and crawl_status polling. Suitable for small crawls (few pages). For large crawls, use crawl_start and crawl_status separately to avoid timeout issues.

Args: url: The starting URL to crawl (required). limit: Maximum pages to crawl (default: 10, max: 100000). depth: Maximum link depth (default: 100000). source: URL discovery source — "all", "sitemaps", or "links" (default: "all"). formats: Output formats — any of ["html", "markdown", "json"] (default: ["html"]). Note: "json" uses Workers AI and incurs additional charges. render: Whether to execute JavaScript via headless browser (default: true). max_age: Cache duration in seconds (default: 86400, max: 604800). modified_since: Unix timestamp — only crawl pages modified since this time. crawl_purposes: Declare content use — any of ["search", "ai-input", "ai-train"]. include_patterns: URL patterns to include (* = any chars except /, ** = any chars). exclude_patterns: URL patterns to exclude (takes priority over include_patterns). include_external_links: Whether to follow links to external domains. include_subdomains: Whether to follow links to subdomains. authenticate: HTTP authentication credentials for protected sites. Example: {"username": "user", "password": "pass"}. extra_http_headers: Custom HTTP headers to send with each crawl request. Example: {"X-API-Key": "abc123"}. json_options: AI-based structured data extraction config (requires "json" in formats). Keys: "prompt" (str) — extraction instruction, "response_format" (dict) — JSON schema for output, "custom_ai" (dict) — custom AI model config. cookies: Browser cookies to set during the crawl. Example: [{"name": "session", "value": "abc", "domain": "example.com"}]. goto_options: Page navigation behaviour. Keys: "waitUntil" (str) — e.g. "networkidle2", "load", "domcontentloaded"; "timeout" (int) — navigation timeout in milliseconds. wait_for_selector: Wait for a DOM element before scraping each page. Keys: "selector" (str), "timeout" (int, ms), "visible" (bool). reject_resource_types: Resource types to block to speed up crawls and reduce cost. Values: "image", "media", "font", "stylesheet", "script", etc. poll_interval: Seconds between status polls (default: 5.0). timeout: Maximum seconds to wait for completion (default: 300.0).

Returns: Final crawl result (same shape as crawl_status) once the job completes, or raises RuntimeError if the timeout is exceeded.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`depth`	No
`limit`	No
`render`	No
`source`	No
`cookies`	No
`formats`	No
`max_age`	No
`timeout`	No
`authenticate`	No
`goto_options`	No
`json_options`	No
`poll_interval`	No
`crawl_purposes`	No
`modified_since`	No
`exclude_patterns`	No
`include_patterns`	No
`wait_for_selector`	No
`extra_http_headers`	No
`include_subdomains`	No
`reject_resource_types`	No
`include_external_links`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

A4.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does so fairly well: it states the blocking/polling behavior (poll_interval, timeout defaults), discloses that exceeding the timeout raises RuntimeError, and warns that 'json' formats use Workers AI and incur additional charges. It does not mention auth requirements or the exact failure modes beyond timeout, keeping it just short of a 5.

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?

The prose is front-loaded and tight, and the long Args block is justified by 22 undocumented parameters, each receiving a single compact line. Slightly verbose in places (multiple multi-line nested-key explanations), but there is essentially no wasted sentence.

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?

For a high-complexity, high-parameter tool, the description covers purpose, sibling routing, every parameter, cost implications, and the return/error contract ('same shape as crawl_status', RuntimeError on timeout). An output schema exists, so return-value detail is appropriately left out; nothing an agent needs to invoke it correctly is missing.

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% across 22 params, so the description must compensate entirely — and it does, documenting defaults, ranges (limit max 100000, max_age max 604800), enum values (source, formats, crawl_purposes, reject_resource_types), priority rules (exclude_patterns 'takes priority'), pattern syntax (* vs **), nested keys for json_options/goto_options/wait_for_selector, and concrete examples for authenticate/extra_http_headers/cookies.

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?

Opens with a specific verb+resource ('Start a crawl and wait for it to complete, returning the final results') and explicitly identifies itself as a composition of crawl_start and crawl_status, which cleanly distinguishes it from those siblings. An agent can tell what it does and how it relates to the other crawl tools without opening any schema.

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?

Gives an explicit when/when-not: 'Suitable for small crawls (few pages). For large crawls, use crawl_start and crawl_status separately to avoid timeout issues.' That names both the alternative tools and the condition that selects them, leaving nothing to inference.

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

Deploy Server