Skip to main content
Glama
mysleekdesigns

CrawlForge MCP Server

crawl_deep

Read-only

Crawl and extract content from multiple pages of a website to build knowledge bases, index documentation, or audit site structure.

Instructions

Use this when you need to discover and optionally extract content from many pages within a site — e.g. building a knowledge base, indexing docs, or auditing all pages. Use map_site first to estimate scope, then crawl_deep for content. Example: crawl_deep({url: "https://docs.example.com", max_depth: 3, max_pages: 200, extract_content: true})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesStarting URL for the crawl
sessionNoShared cookie-jar/session for login-then-crawl workflows
max_depthNoMaximum crawl depth from starting URL
max_pagesNoMaximum number of pages to crawl
concurrencyNoNumber of concurrent requests
domain_filterNoPer-domain allow/deny lists and crawl rules
respect_robotsNoRespect robots.txt directives
extract_contentNoExtract page content during crawl
follow_externalNoFollow links to external domains
exclude_patternsNoURL patterns to exclude (regex)
include_patternsNoURL patterns to include (regex)
content_max_lengthNoMaximum characters of page content to include per page (default 500); sets a truncated flag when trimmed
enable_link_analysisNoCompute PageRank/link-graph analysis over crawled pages
import_filter_configNoJSON string of a previously exported domain-filter config
link_analysis_optionsNoPageRank tuning options
Behavior3/5

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

Annotations already cover readOnlyHint and openWorldHint. Description adds that content extraction is optional but does not elaborate on other behavioral aspects like respects robots.txt or potential long runtime. No contradiction with annotations.

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?

Description is concise, front-loaded with purpose, includes a workflow suggestion and example. Slightly longer than necessary but efficient.

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

Completeness3/5

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

Given the complexity (15 params, nested objects, no output schema), the description provides sufficient context for usage but lacks details on return values or time considerations. Adequate but not complete.

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% with good parameter descriptions. Description includes an example call but adds no additional semantics beyond what the schema already provides.

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?

Description clearly states the tool discovers and optionally extracts content from many pages within a site, with specific use cases. It distinguishes from siblings by mentioning map_site as a prerequisite, but does not explicitly contrast with all sibling tools.

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?

Description specifies when to use (for multi-page discovery/extraction) and suggests using map_site first, providing a clear workflow. Lacks explicit when-not-to-use guidance.

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

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