Skip to main content
Glama

crw_scrape

Scrape any web page to get clean markdown, HTML, or links. Optionally render JavaScript, filter with CSS selectors, and wait for dynamic content.

Instructions

Scrape a single URL and return its content as markdown, HTML, or links. Use this to extract content from any web page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
excludeTagsNoCSS selectors to exclude from output
formatsNoOutput formats (default: ["markdown"])
includeTagsNoCSS selectors to include (only content matching these selectors)
onlyMainContentNoExtract only the main content, removing nav/footer/etc (default: true)
renderJsNoRender JavaScript before extracting (true = force JS, false = HTTP only, omit = auto-detect or use the server's render_js_default)
rendererNoPin 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.
urlYesThe URL to scrape
waitForNoMilliseconds to wait after JS rendering for late content/XHRs
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states the basic purpose and output types, omitting details about JS rendering, wait times, CSS filtering, or error behavior, despite the schema exposing these parameters.

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?

Two sentences, front-loaded with purpose, no fluff. Every word earns its place.

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?

Despite 8 parameters and no output schema or annotations, the description provides no context on return format, error handling, limitations, or advanced features. It is insufficient for a tool of this complexity.

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 baseline is 3. The description does not add any additional meaning or usage tips beyond what the schema already provides for each parameter.

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 explicitly states the verb 'scrape' and resource 'single URL', and specifies output formats (markdown, HTML, links). It clearly distinguishes from sibling tools like crw_crawl (likely for multiple URLs) by focusing on a single URL.

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 gives clear when-to-use guidance ('extract content from any web page'), but does not explicitly mention when not to use or provide alternatives among siblings.

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/us/crw'

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