Skip to main content
Glama

batch_crawl

Crawl up to 3 URLs concurrently with automatic fallback on failure. Optionally save each page as markdown plus an index.json to a local directory.

Instructions

Crawl multiple URLs with fallback. Max 3 URLs per call. Use output_path (directory) to persist full per-URL markdown + index.json; the return shape stays a list, each success item gets an output_file key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYesURLs to crawl (max 3)
base_timeoutNoTimeout per URL (default: 30)
generate_markdownNoGenerate markdown (default: True)
extract_mediaNoExtract media (default: False)
wait_for_jsNoWait for JS (default: False)
output_pathNoAbsolute directory path to persist per-URL markdown files + index.json. Existing regular files at this path are rejected; otherwise the directory is created if missing (dot-containing names like /tmp/run.v1 are fine). The list return shape is preserved; each successful item gains an 'output_file' key. Failed items (success=False) are NOT written as .md but still appear in index.json with file=null.
include_content_in_responseNoWhen True (with output_path), keep full markdown/content in each list item. Defaults to False so the response stays token-efficient.
overwriteNoOverwrite existing per-URL files inside output_path. Defaults to False (existing files cause an output_path_exists error, returned as a single-element list).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Without annotations, the description covers key behaviors: output_path creation and validation, per-URL file writing, error handling for failures and existing files, and the effect of include_content_in_response. It does not mention authentication or rate limits.

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 a single, compact paragraph that front-loads the core purpose and constraints. It packs significant detail without redundancy, though it could benefit from slight restructuring for readability.

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?

Given the tool's complexity (8 parameters, output schema present), the description covers most behavioral aspects and parameter interactions. A minor gap is the lack of elaboration on the fallback mechanism mentioned in the title.

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 coverage is 100%, but the description adds meaningful context for output_path (e.g., dot-containing names allowed, index.json handling) and include_content_in_response (token efficiency). This goes beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool crawls multiple URLs with fallback and specifies a maximum of 3 URLs per call. It identifies the resource and action, but does not explicitly differentiate from siblings like multi_url_crawl or crawl_url_with_fallback.

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 provides guidance on using output_path for persistence and notes constraints like maximum URLs. However, it lacks explicit context on when to choose this tool over alternatives or when not to use it.

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/walksoda/crawl-mcp'

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