Skip to main content
Glama
laurentvv

Crawl4AI MCP

by laurentvv

crawl

Extract website content and save it as structured markdown. Configure parameters like depth, CSS selectors, and anti-bot bypass for tailored results.

Instructions

Crawls a website and saves its content as structured markdown to a file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to crawl
max_depthNoMaximum crawling depth
include_externalNoWhether to include external links
verboseNoEnable verbose output
output_fileNoPath to output file (generated if not provided)
wait_for_selectorNoCSS selector to wait for before extracting content. Useful for single-page applications.
return_contentNoWhether to return the extracted content directly in the MCP response
magicNoEnable magic mode to bypass anti-bots and simulate a real browser
css_selectorNoSpecific CSS selector to extract only targeted elements from the page
js_codeNoCustom JavaScript code to execute on the page before extraction (Requires CRAWL4AI_MCP_ALLOW_JS=true environment variable)
session_idNoPersistent session identifier to keep cookies and browser state across requests
delay_before_return_htmlNoDelay in seconds to wait before extracting HTML (useful for heavy JS pages)
Behavior2/5

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

With no annotations, the description carries full burden but only mentions saving to file, ignoring the return_content parameter's behavior and other complex features like magic mode and JS execution.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise but underspecified for the complexity; it does not front-load key behavioral details.

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

Completeness2/5

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

Given the 12 parameters and lack of output schema, the description fails to explain return values, side effects, or important behavioral nuances.

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%, so the baseline is 3. The description adds no additional parameter meaning beyond what's in the schema.

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 the action (crawls) and the output (structured markdown to a file), leaving no ambiguity about what the tool does.

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?

No guidance is provided on when to use this tool versus alternatives; no context about prerequisites or appropriate scenarios.

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/laurentvv/crawl4ai-mcp'

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