Skip to main content
Glama
mendableai

Firecrawl MCP Server

by mendableai

firecrawl_crawl

Extract content from multiple website pages by starting a crawl job. Use for comprehensive coverage of related pages, with options to control depth and scope.

Instructions

Starts a crawl job on a website and extracts content from all pages.

Best for: Extracting content from multiple related pages, when you need comprehensive coverage. Not recommended for: Extracting content from a single page (use scrape); when token limits are a concern (use map + batch_scrape); when you need fast results (crawling can be slow). Warning: Crawl responses can be very large and may exceed token limits. Limit the crawl depth and number of pages, or use map + batch_scrape for better control. Common mistakes: Setting limit or maxDiscoveryDepth too high (causes token overflow) or too low (causes missing pages); using crawl for a single page (use scrape instead). Using a /* wildcard is not recommended. Prompt Example: "Get all blog posts from the first two levels of example.com/blog." Usage Example:

{
  "name": "firecrawl_crawl",
  "arguments": {
    "url": "https://example.com/blog/*",
    "maxDiscoveryDepth": 5,
    "limit": 20,
    "allowExternalLinks": false,
    "deduplicateSimilarURLs": true,
    "sitemap": "include"
  }
}

Returns: Operation ID for status checking; use firecrawl_check_crawl_status to check progress.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
promptNo
excludePathsNo
includePathsNo
maxDiscoveryDepthNo
sitemapNo
limitNo
allowExternalLinksNo
allowSubdomainsNo
crawlEntireDomainNo
delayNo
maxConcurrencyNo
webhookNo
deduplicateSimilarURLsNo
ignoreQueryParametersNo
scrapeOptionsNo
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it warns about large responses potentially exceeding token limits, mentions crawling can be slow, explains the return value is an operation ID requiring status checking, and notes the need to limit depth/pages. It doesn't cover all potential behaviors like error conditions or authentication requirements.

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 well-structured with clear sections (Best for, Not recommended for, Warning, Common mistakes, Prompt Example, Usage Example, Returns) that make information easily scannable. Every sentence serves a purpose - there's no redundant or unnecessary content despite the comprehensive coverage.

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 16 parameters, no annotations, and no output schema, the description does remarkably well. It covers purpose, usage guidelines, behavioral warnings, parameter examples, and return value explanation. The main gap is that it doesn't fully document all 16 parameters' semantics, but given the complexity, it provides substantial contextual information.

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?

With 0% schema description coverage and 16 parameters, the description adds significant value beyond the bare schema. It provides context for several parameters through the usage example (url, maxDiscoveryDepth, limit, allowExternalLinks, deduplicateSimilarURLs, sitemap) and warns about misconfiguring limit/maxDiscoveryDepth. However, it doesn't explain all 16 parameters' semantics, leaving some undocumented.

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 the tool's purpose with specific verbs ('starts a crawl job', 'extracts content from all pages') and distinguishes it from siblings like 'scrape' for single pages and 'map + batch_scrape' for token-limited scenarios. It explicitly defines the resource (website) and scope (multiple related pages).

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?

The description provides explicit guidance with dedicated sections: 'Best for' (comprehensive coverage of multiple pages), 'Not recommended for' (single pages, token limits, speed needs), and 'Common mistakes' (parameter misconfigurations, incorrect use cases). It names specific alternatives like 'scrape' and 'map + batch_scrape' for different scenarios.

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/mendableai/firecrawl-mcp-server'

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