CrawlForge MCP Server

batch_scrape

Read-only

Scrape 2-50 URLs in a single call with sync or async execution, returning structured data in multiple formats like JSON, HTML, markdown, or text.

Instructions

Use this to scrape 2-50 URLs in one call - product pages, news articles, competitor pages. Never loop scrape over a URL list. mode:"sync" returns results directly for up to ~25 URLs; mode:"async" with a webhook for larger batches, then get_batch_results. Not for one URL (scrape) or for discovering URLs (map_site). Cost: 5 credits. Example: batch_scrape({urls: ["https://a.com","https://b.com"], formats: ["json"], maxConcurrency: 5})

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No	Processing mode: sync (wait) or async (background)	sync
`urls`	Yes	Array of URLs or URL objects to scrape
`formats`	No	Output formats for scraped content
`webhook`	No	Webhook configuration for async job notifications
`pageSize`	No	Number of results per page
`jobOptions`	No	Job management options for async processing
`redact_pii`	No	Redact personal data from the text this call returns, before it reaches your context window. true means the free regex pass over EMAIL, PHONE, FINANCIAL and SECRET. The result carries redaction:{entities,count}. Default: off
`user_agent`	No	Override the outbound User-Agent. CrawlForge identifies itself honestly by default; use this only for targets you have your own agreement with.
`includeFailed`	No	Include failed URLs in results
`maxConcurrency`	No	Maximum concurrent scraping requests
`respect_robots`	No	Respect the target site's robots.txt (default: true). Setting this to false is honoured, returns a warning in the response, and is recorded against your API key — it is your decision, not a silent default.
`includeMetadata`	No	Include page metadata in results
`extractionSchema`	No	Schema for structured data extraction from each URL
`max_inline_chars`	No	Largest result to return inline, in characters of its JSON. Over it, the call returns a preview plus a result_handle for read_result instead of the whole result (default 40,000; env CRAWLFORGE_MAX_INLINE_CHARS)
`delayBetweenRequests`	No	Delay in milliseconds between requests

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed8 schema fields changedv6.0.0Sep 6, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / extractionSchema / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
removedInput schema / properties / jobOptions / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / max_inline_chars

Added value: +{
+  "description": "Largest result to return inline, in characters of its JSON. Over it, the call returns a preview plus a result_handle for read_result instead of the whole result (default 40,000; env CRAWLFORGE_MAX_INLINE_CHARS)",
+  "maximum": 10000000,
+  "minimum": 1000,
+  "type": "integer"
+}

addedInput schema / properties / redact_pii

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "properties": {
+        "entities": {
+          "description": "Which classes to redact, case-insensitive: EMAIL, PHONE, FINANCIAL, SECRET, plus PERSON and LOCATION when mode is \"model\". Omitted or empty means all four regex classes (and both model classes in \"model\" mode). An unknown name, or a model-only name without mode:\"model\", is rejected",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "mode": {
+          "description": "\"fast\" (default) is regex only and free; \"model\" adds an Ollama NER pass for PERSON and LOCATION (+3 credits once per call)",
+          "enum": [
+            "fast",
+            "model"
+          ],
+          "type": "string"
+        },
+        "replace_style": {
+          "description": "\"tag\" (default) writes <EMAIL>, \"mask\" writes [REDACTED], \"remove\" deletes the value",
+          "enum": [
+            "tag",
+            "mask",
+            "remove"
+          ],
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  ],
+  "description": "Redact personal data from the text this call returns, before it reaches your context window. true means the free regex pass over EMAIL, PHONE, FINANCIAL and SECRET. The result carries redaction:{entities,count}. Default: off"
+}

changedInput schema / properties / urls / items / anyOf

Previous value: -[
-  {
-    "format": "uri",
-    "type": "string"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "headers": {
-        "additionalProperties": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "metadata": {
-        "additionalProperties": {},
-        "type": "object"
-      },
-      "selectors": {
-        "additionalProperties": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "timeout": {
-        "maximum": 30000,
-        "minimum": 1000,
-        "type": "number"
-      },
-      "url": {
-        "format": "uri",
-        "type": "string"
-      }
-    },
-    "required": [
-      "url"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "format": "uri",
+    "type": "string"
+  },
+  {
+    "properties": {
+      "headers": {
+        "additionalProperties": {
+          "type": "string"
+        },
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "metadata": {
+        "additionalProperties": {},
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "selectors": {
+        "additionalProperties": {
+          "type": "string"
+        },
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "timeout": {
+        "maximum": 30000,
+        "minimum": 1000,
+        "type": "number"
+      },
+      "url": {
+        "format": "uri",
+        "type": "string"
+      }
+    },
+    "required": [
+      "url"
+    ],
+    "type": "object"
+  }
+]

removedInput schema / properties / webhook / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / webhook / properties / headers / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedv5.4.0Aug 29, 2026

addedInput schema / properties / respect_robots

Added value: +{
+  "description": "Respect the target site's robots.txt (default: true). Setting this to false is honoured, returns a warning in the response, and is recorded against your API key — it is your decision, not a silent default.",
+  "type": "boolean"
+}

addedInput schema / properties / user_agent

Added value: +{
+  "description": "Override the outbound User-Agent. CrawlForge identifies itself honestly by default; use this only for targets you have your own agreement with.",
+  "type": "string"
+}

Changed1 schema field changedv5.0.4Aug 21, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv4.10.0Jul 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds value beyond that by disclosing cost (5 credits), the sync/async behavior difference, the webhook requirement for async, and the existence of get_batch_results. It doesn't contradict annotations. A small gap is that it doesn't describe return format or pagination, but that is secondary given the annotation coverage.

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 three sentences plus an example. It front-loads the purpose, immediately states the key usage constraint (no looping), and provides a concrete example. Every sentence earns its place; no fluff or repetition.

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?

For a complex tool with 15 parameters, nested objects, and no output schema, the description covers the most critical decision points: when to use it, how to scale via modes, cost, and an example. It doesn't explain all parameters, but the schema does that. It also points to get_batch_results for async retrieval. Slight gap: it doesn't describe the sync return structure or pagination, but that is not explicitly required given the schema and the tool's nature.

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 every parameter is described in the schema. The description adds an example that illustrates urls, formats, and maxConcurrency, and it explains the mode parameter's semantics (sync vs async) beyond the enum. However, it doesn't clarify other parameters like redact_pii, extractionSchema, or jobOptions, relying on the schema. This is adequate given the schema's thoroughness.

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 opens with a specific verb and resource: 'scrape 2-50 URLs in one call' and names target content types. It immediately distinguishes itself from siblings by stating it is 'Not for one URL (scrape) or for discovering URLs (map_site)', so an agent can separate it from the many sibling scraping tools without opening schemas.

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?

It gives explicit when-to-use guidance: 'Never loop scrape over a URL list' and explains the mode choice (sync for up to ~25 URLs, async with webhook for larger batches). It names the alternatives (scrape, map_site) and the condition that selects them, plus an example call. This is comprehensive routing guidance.

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

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/mysleekdesigns/crawlforge-mcp'

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