Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

web_scrape

Scrape any public URL into clean markdown, HTML, links, or metadata. Automatically switches to a real browser when pages require JavaScript or block HTTP requests.

Instructions

Scrape a URL into markdown, HTML, links or metadata. Fetches a single public URL and returns clean content in the requested formats (markdown, html, raw_html, links, metadata). The request body IS the ScrapeOption object itself — e.g. {"url": "https://example.com"} — do not wrap it in an extra key. With render=auto the request starts as a fast HTTP fetch and escalates to a real browser when the page is blocked or rendered with JavaScript; backend only pins a specific headless-browser engine for the browser tier and is not a render mode. only_main_content (default true) strips navigation, headers, footers and other boilerplate before conversion. Only public pages are supported; respect each site's terms of use and robots directives. A handful of popular sites (Amazon, Reddit, Yelp, LinkedIn, and others) already have a dedicated, more reliable endpoint elsewhere in this API — a failed scrape against one of them names it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scrapeOptionYesScrape options

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / scrapeOption / properties
      Added value: +{
+  "backend": {
+    "type": "string"
+  },
+  "formats": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "max_age": {
+    "type": "integer"
+  },
+  "only_main_content": {
+    "type": "boolean"
+  },
+  "proxy": {
+    "type": "string"
+  },
+  "render": {
+    "enum": [
+      "auto",
+      "http",
+      "browser",
+      "unblocker"
+    ],
+    "type": "string"
+  },
+  "store_in_cache": {
+    "type": "boolean"
+  },
+  "url": {
+    "type": "string"
+  },
+  "wait_for": {
+    "type": "integer"
+  }
+}
    • addedInput schema / properties / scrapeOption / required
      Added value: +[
+  "url"
+]
  2. Addedv1.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It thoroughly describes the render escalation mechanism (from fast HTTP to browser), defaults (only_main_content=true), and constraints (public pages only, respect terms). It does not detail what happens on failure beyond naming alternatives, or auth requirements, but this is a public scrape tool so expectations are clear.

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 description is fairly long but each sentence adds distinct value. It starts with the core action and formats, then clarifies the request body format, then explains render modes, defaults, and alternatives. It could be tightened by trimming some parentheticals, but there is no filler.

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

Completeness4/5

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

The tool has a nested object schema and no output schema. The description covers request format, key options, default behavior, and routing to specialized tools. It does not explain the structure of returned data (e.g., which formats return what), but given the tool's general purpose and the absence of a formal output schema, it is sufficiently complete for an agent to invoke it correctly.

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

Parameters4/5

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

Schema description coverage is 100% for the single wrapper parameter, but the nested properties are only shown as type names. The description adds meaning by explaining the critical request body shape (do not wrap in extra key), the purpose of render='auto', the behavior of only_main_content, and the list of formats. It doesn't spell out each parameter (proxy, max_age, wait_for), but for a general tool the most important ones are covered.

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 states a specific verb ('scrape'), a resource ('URL'), and the output types (markdown, HTML, links, metadata). It clearly distinguishes itself from the many site-specific scrapers in the sibling list by being the generic fallback, and even names examples of sites that have dedicated endpoints.

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?

The description explicitly explains when to use this tool: for scraping public URLs, and when not to use it: for popular sites like Amazon, Reddit, Yelp, LinkedIn, where dedicated endpoints exist. It also explains that a failed scrape against such a site will name the alternative, providing a clear routing strategy.

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

Deploy Server

Other Tools