Firecrawl MCP Server

Firecrawl crawl status

firecrawl_check_crawl_status

Read-only

Check an existing crawl by ID to retrieve its current status, progress, and available results without starting or modifying the job.

Instructions

Retrieve the current status, progress, and available results for an existing crawl ID. This only reads Firecrawl job state and does not start or modify the crawl.

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": {
      "id": "<id>"
    },
    "name": "firecrawl_check_crawl_status"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

Name	Required	Description
`id`	No	Crawl identifier, for `firecrawl_check_crawl_status`.
`url`	No	The URL the crawl started from.
`data`	No	Scraped documents collected by the crawl.
`next`	No	URL of the next page of results, when the data is paginated.
`error`	No	Error message or error object when the call did not succeed.
`total`	No	Pages the crawl expects to visit.
`status`	No	Crawl state, such as `scraping`, `completed`, or `failed`.
`success`	No	Whether the API call succeeded.
`warning`	No	Non-fatal warning about the result.
`completed`	No	Pages crawled so far.
`expiresAt`	No	When the crawl results expire.
`agent_hints`	No	Optional response guidance from the Firecrawl API.
`creditsUsed`	No	Credits the crawl consumed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.28.2Nov 4, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, and the description largely restates that read-only profile rather than extending it. It adds no context on whether partial results appear mid-crawl, how states progress, or whether repeated polling is expected.

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 short sentences, front-loaded with the outcome, with the scoping disclaimer second. No filler and nothing redundant within the text itself.

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?

An output schema exists, so return values need no explanation, and the tool is a single-parameter read. The remaining gap is stating where the crawl ID comes from and that callers may need to poll until the status is terminal.

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 0% and the schema describes 'id' only as a bare string, so the description's phrase 'existing crawl ID' is the only signal that this value is a crawl job identifier rather than a URL or scrape ID. That is useful but minimal for a low-coverage single-param schema.

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?

States a specific verb and resource ('Retrieve the current status, progress, and available results') and pins the input to an 'existing crawl ID'. The clause 'does not start or modify the crawl' implicitly separates it from firecrawl_crawl, though no sibling is named explicitly.

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?

Usage is clearly implied as a follow-up call on an ID returned by a crawl, and the negative guidance ('does not start or modify') rules out using it to launch work. It stops short of naming firecrawl_crawl as the producer of the ID or firecrawl_agent_status as the parallel for agent jobs, and gives no polling guidance.

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