crw-mcp

Overview Schema Source Related Servers Discussions Admin

Scrape URL

crw_scrape

Read-onlyIdempotent

Scrape any URL and convert it to clean markdown, HTML, links, or images. Choose formats, wait for JS-rendered content, and filter by CSS selectors for targeted extraction.

Instructions

Scrape one URL to markdown, HTML, or links.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	URL to scrape
`formats`	No	Output formats (default ["markdown"])
`waitFor`	No	Ms to wait after JS render for late content
`renderJs`	No	Force JS render (true), HTTP-only (false), omit = auto
`renderer`	No	Pin renderer; browser tiers imply renderJs:true (default auto). 'camoufox' needs the opt-in tier configured. 'impersonated-http' is JS-less Chrome-TLS impersonation, never renderJs.
`maxLength`	No	Max chars per content field; 0 = unbounded (default ~15000)
`excludeTags`	No	CSS selectors to exclude
`includeTags`	No	CSS selectors to include
`onlyMainContent`	No	Strip nav/footer; main content only (default true)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.35.1Sep 11, 2026

changedInput schema / properties / renderer / description

Previous value: -"Pin renderer; non-auto hard-pins and implies renderJs:true (default auto). 'camoufox' requires the server's opt-in camoufox tier to be configured."New value: +"Pin renderer; browser tiers imply renderJs:true (default auto). 'camoufox' needs the opt-in tier configured. 'impersonated-http' is JS-less Chrome-TLS impersonation, never renderJs."

changedInput schema / properties / renderer / enum

Previous value: -[
-  "auto",
-  "lightpanda",
-  "chrome",
-  "playwright",
-  "camoufox"
-]New value: +[
+  "auto",
+  "lightpanda",
+  "chrome",
+  "playwright",
+  "camoufox",
+  "impersonated-http"
+]

Changed1 schema field changedv0.30.0Aug 10, 2026

changedInput schema / properties / formats / items / enum

Previous value: -[
-  "markdown",
-  "html",
-  "links"
-]New value: +[
+  "markdown",
+  "html",
+  "links",
+  "images"
+]

Changed2 schema fields changedv0.18.0Jun 23, 2026

changedInput schema / properties / renderer / description

Previous value: -"Pin renderer; non-auto hard-pins and implies renderJs:true (default auto)"New value: +"Pin renderer; non-auto hard-pins and implies renderJs:true (default auto). 'camoufox' requires the server's opt-in camoufox tier to be configured."

changedInput schema / properties / renderer / enum

Previous value: -[
-  "auto",
-  "lightpanda",
-  "chrome",
-  "playwright"
-]New value: +[
+  "auto",
+  "lightpanda",
+  "chrome",
+  "playwright",
+  "camoufox"
+]

Changed9 schema fields changedv0.16.0Jun 18, 2026

changedInput schema / properties / excludeTags / description

Previous value: -"CSS selectors to exclude from output"New value: +"CSS selectors to exclude"

changedInput schema / properties / formats / description

Previous value: -"Output formats (default: [\"markdown\"])"New value: +"Output formats (default [\"markdown\"])"

changedInput schema / properties / includeTags / description

Previous value: -"CSS selectors to include (only content matching these selectors)"New value: +"CSS selectors to include"

addedInput schema / properties / maxLength

Added value: +{
+  "description": "Max chars per content field; 0 = unbounded (default ~15000)",
+  "minimum": 0,
+  "type": "integer"
+}

changedInput schema / properties / onlyMainContent / description

Previous value: -"Extract only the main content, removing nav/footer/etc (default: true)"New value: +"Strip nav/footer; main content only (default true)"

changedInput schema / properties / renderJs / description

Previous value: -"Render JavaScript before extracting (true = force JS, false = HTTP only, omit = auto-detect or use the server's render_js_default)"New value: +"Force JS render (true), HTTP-only (false), omit = auto"

changedInput schema / properties / renderer / description

Previous value: -"Pin this request to a specific renderer. \"auto\" (default if omitted) uses the configured fallback chain. Other values hard-pin to a single renderer with no fallback. Pinning a non-auto value implies renderJs:true unless renderJs:false is set explicitly."New value: +"Pin renderer; non-auto hard-pins and implies renderJs:true (default auto)"

changedInput schema / properties / url / description

Previous value: -"The URL to scrape"New value: +"URL to scrape"

changedInput schema / properties / waitFor / description

Previous value: -"Milliseconds to wait after JS rendering for late content/XHRs"New value: +"Ms to wait after JS render for late content"

Addedv0.9.1May 16, 2026
Removedv0.8.3May 15, 2026

Changed3 schema fields changedv0.6.2May 10, 2026

addedInput schema / properties / renderJs

Added value: +{
+  "description": "Render JavaScript before extracting (true = force JS, false = HTTP only, omit = auto-detect or use the server's render_js_default)",
+  "type": "boolean"
+}

addedInput schema / properties / renderer

Added value: +{
+  "description": "Pin this request to a specific renderer. \"auto\" (default if omitted) uses the configured fallback chain. Other values hard-pin to a single renderer with no fallback. Pinning a non-auto value implies renderJs:true unless renderJs:false is set explicitly.",
+  "enum": [
+    "auto",
+    "lightpanda",
+    "chrome",
+    "playwright"
+  ],
+  "type": "string"
+}

addedInput schema / properties / waitFor

Added value: +{
+  "description": "Milliseconds to wait after JS rendering for late content/XHRs",
+  "type": "integer"
+}

First observedv1.0.0Apr 13, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds output format context but does not mention rendering behavior, potential delays, or response format. It does not contradict annotations and provides modest additional info about what the tool produces.

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 a single sentence that wastes no words and leads with the action and resource. It is appropriately concise for a tool with a well-documented schema.

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?

Given the tool has 9 parameters, only one required, and no output schema, the description is minimal. It lacks usage guidance and does not mention the 'images' format even though it is in the enum. However, the schema descriptions are thorough, so the agent can infer parameter behavior. The description is adequate but leaves gaps in when-to-use and output details.

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 each parameter has a description. The tool description does not add parameter-specific meaning beyond that, and it does not clarify ambiguous terms. Baseline of 3 is appropriate given the schema fully documents the parameters.

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 'Scrape one URL to markdown, HTML, or links' clearly identifies the verb (scrape), the resource (one URL), and the output types. It distinguishes from siblings like crw_crawl (multiple URLs) and crw_extract (structured data) by emphasizing a single URL and specific formats.

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

Usage Guidelines3/5

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

The description implies single-page scraping but does not explicitly state when to prefer this over siblings like crw_crawl or crw_extract. There are no exclusions, alternatives, or conditions. The phrase 'one URL' hints at the scope, but no explicit guidance is provided.

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

Deploy Server

Scrape URL

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools