Skip to main content
Glama

deep_crawl_site

Read-only

Crawl multiple pages from a starting URL with configurable depth and strategy. Save results as per-URL markdown files and a metadata index.

Instructions

Crawl multiple pages from a site with configurable depth. Use output_path (directory) to persist per-URL markdown files + index.json; the response is then slimmed to metadata only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesStarting URL
max_depthNoLink depth (1-2)
max_pagesNoMax pages (max: 10)
crawl_strategyNo'bfs'|'dfs'|'best_first'bfs
include_externalNoFollow external links
url_patternNoURL filter pattern
score_thresholdNoMin relevance 0-1
extract_mediaNoExtract media
base_timeoutNoTimeout per page
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). When set, the response is slimmed to metadata+file paths. Failed items (success=False) are NOT written as .md but still recorded in index.json with file=null.
include_content_in_responseNoWhen True (with output_path set), also include per-page content/markdown in the response items. 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).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

The description discloses that writing files to output_path is a side effect, and that the response is slimmed when output_path is set. This adds value beyond the readOnlyHint annotation, but it does not cover all behavioral traits (e.g., rate limits, auth).

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 and key behavior. Every sentence earns its place; no redundancy with schema.

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 tool complexity (12 parameters) and presence of output schema, the description is fairly complete. It explains the main output_path feature and behavior, but does not elaborate on other parameters or when to use depth vs alternatives.

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

Parameters5/5

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

The description adds significant meaning to parameters like output_path, include_content_in_response, and overwrite, explaining their effects on response and file persistence. Schema coverage is 100% but the description enriches understanding.

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 crawls multiple pages from a site with configurable depth, using a verb+resource structure. It distinguishes from siblings like crawl_url by mentioning multi-page and output persistence.

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 implies usage for multi-page crawling with depth, but does not explicitly state when to use this tool versus alternatives like crawl_url or batch_crawl. No when-not or exclusions are provided.

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