Skip to main content
Glama

multi_url_crawl

Read-only

Crawl up to 5 URLs with pattern-based configuration, save each page as markdown files and an index.json to a directory.

Instructions

Multi-URL crawl with pattern-based config. Max 5 URL patterns 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
url_configurationsYesURL-config mapping (max 5 URLs). Example: {'https://site1.com': {'wait_for_js': true}}
pattern_matchingNoPattern: 'wildcard' or 'regex' (default: wildcard)wildcard
default_configNoDefault config
base_timeoutNoTimeout per URL (default: 30)
max_concurrentNoMax concurrent (default: 3)
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 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.
overwriteNoOverwrite existing per-URL files inside output_path. Defaults to False.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description details output_path behavior: persisting per-URL markdown + index.json, return shape preservation, output_file key, and handling of failed items. This adds significant value beyond annotations.

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 with no wasted words, front-loaded with action and key constraints. Highly efficient.

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

Completeness5/5

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

Given complexity (8 parameters, nested objects, output schema), the description covers core behavior, output path details, and return shape. Output schema exists, so return values are explained elsewhere.

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 constraints like max 5 URLs and clarifies return shape, which are not in schema. This provides meaningful extra context.

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 clearly states it performs multi-URL crawls with pattern-based config, distinguishing it from single-URL tools like crawl_url. It specifies max 5 URL patterns and mentions output persistence, which is unique.

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 implies use for multiple URLs with pattern matching and mentions max 5 patterns. It does not explicitly exclude other tools but provides enough context for selection.

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