Skip to main content
Glama

Firecrawl by Nova (CIVAI)

firecrawl_crawl

Start a multi-page crawl at a website URL, poll it to a terminal state, and return the final status and collected data. Scope can be bounded with include/exclude paths, depth, page limit, subdomain/external-link controls, sitemap handling, delay, and scrape options.

Crawl results can be large; use conservative limits when full-site coverage is unnecessary. Webhooks and interactive scrape actions are unavailable in safe mode. zeroDataRetention runs the crawl with zero data retention and requires an eligible authenticated account. Returns the crawl ID, status, and page data.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "firecrawl_crawl"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
delayNo
limitNo
promptNo
sitemapNo
objectiveNoThe user's underlying goal in one sentence, not a restatement of this call's arguments. Reuse it across related calls. Firecrawl uses it to learn what agents need and improve its results. No personal data, secrets or the user's exact words.
excludePathsNo
includePathsNo
scrapeOptionsNo
conversationIdNoconversationId from any earlier Firecrawl tool result in this conversation; after parallel calls, any one of theirs. Omit only on the first call of a conversation; the result returns one to pass on every later call.
maxConcurrencyNo
allowSubdomainsNo
crawlEntireDomainNo
maxDiscoveryDepthNo
zeroDataRetentionNo
allowExternalLinksNo
ignoreQueryParametersNo
deduplicateSimilarURLsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / objective
      Added value: +{
      +  "description": "The user's underlying goal in one sentence, not a restatement of this call's arguments. Reuse it across related calls. Firecrawl uses it to learn what agents need and improve its results. No personal data, secrets or the user's exact words.",
      +  "maxLength": 5000,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • removedInput schema / properties / scrapeOptions / properties / zeroDataRetention
      Removed value: -{
      -  "type": "boolean"
      -}
    • addedInput schema / properties / zeroDataRetention
      Added value: +{
      +  "type": "boolean"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / scrapeOptions / properties / jsonOptions / properties / schema / additionalProperties
      Previous value: -{}New value: +true
  4. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With zero annotations the description carries the full burden, and it discloses the important traits: the call blocks while polling to a terminal state, results can be large, webhooks/interactive actions are disabled in safe mode, and zeroDataRetention requires an eligible authenticated account. It omits cost/credit implications and any rate-limit or concurrency caveat, which matters given a credit-usage sibling exists.

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?

Front-loaded with the action and lifecycle, then scope controls, then caveats. Sentences are dense but each carries distinct information; the only slight waste is re-listing the scope knobs that also appear in the schema.

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?

It does state what comes back (crawl ID, status, page data) and explains the blocking poll, which covers a lot for a tool with no output schema and no annotations. Still, for an 18-parameter nested-schema crawl it leaves conversationId threading, cost/credit behavior, and concurrency semantics undocumented, which an agent needs before firing an expensive crawl.

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?

With 18 parameters at 11% schema description coverage, the description does meaningful work by naming scope controls (include/exclude paths, depth, page limit, subdomain/external-link, sitemap, delay, scrape options) and explaining the zeroDataRetention eligibility constraint. But conversationId, prompt, objective, maxConcurrency, ignoreQueryParameters, and deduplicateSimilarURLs get no explanation anywhere, and the crawlEntireDomain vs allowSubdomains distinction is left ambiguous.

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 opens with a specific verb and resource ('Start a multi-page crawl at a website URL') and adds the full lifecycle (poll to terminal state, return status and data). 'Multi-page' implicitly separates it from the single-page scrape sibling, but it never names that sibling, so differentiation is inferential rather than explicit.

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?

It gives real usage advice ('use conservative limits when full-site coverage is unnecessary') and flags unavailable features in safe mode. However, it never states when to prefer this over firecrawl_scrape, firecrawl_map, or the status-check sibling, so the agent must infer the routing decision.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources