Firecrawl MCP Server

firecrawl_check_crawl_status

Monitor the progress and retrieve results of web crawling jobs initiated through the Firecrawl MCP Server by providing the crawl job ID.

Instructions

Check the status of a crawl job.

Usage Example:

{
  "name": "firecrawl_check_crawl_status",
  "arguments": {
    "id": "550e8400-e29b-41d4-a716-446655440000"
  }
}

Returns: Status and progress of the crawl job, including results if available.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Crawl job ID to check

Implementation Reference

src/index.ts:1136-1155 (handler)

The implementation of the firecrawl_check_crawl_status tool handler in the switch case.

      case 'firecrawl_check_crawl_status': {
        if (!isStatusCheckOptions(args)) {
          throw new Error('Invalid arguments for firecrawl_check_crawl_status');
        }
        const response = await client.checkCrawlStatus(args.id);
        if (!response.success) {
          throw new Error(response.error);
        }
        const status = `Crawl Status:
Status: ${response.status}
Progress: ${response.completed}/${response.total}
Credits Used: ${response.creditsUsed}
Expires At: ${response.expiresAt}
${
  response.data.length > 0 ? '\nResults:\n' + formatResults(response.data) : ''
}`;
        return {
          content: [{ type: 'text', text: trimResponseText(status) }],
          isError: false,
        };

src/index.ts:387-400 (registration)

Registration of the firecrawl_check_crawl_status tool.

const CHECK_CRAWL_STATUS_TOOL: Tool = {
  name: 'firecrawl_check_crawl_status',
  description: `
Check the status of a crawl job.

**Usage Example:**
\`\`\`json
{
  "name": "firecrawl_check_crawl_status",
  "arguments": {
    "id": "550e8400-e29b-41d4-a716-446655440000"
  }
}
\`\`\`

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.12.0Mar 17, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations provided, so description carries burden. It mentions returns 'status and progress' but lacks details on polling behavior, rate limits, or error recovery. Basic transparency but incomplete for an operation that may be called repeatedly.

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?

Very concise at one sentence plus a usage example. The example provides clear invocation format. No filler, but could include a line about return structure without hurting conciseness.

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?

For a simple status-check tool with one parameter and no output schema, the description is adequate but lacks context like prerequisite (must have called firecrawl_crawl first) and expected statuses (e.g., 'completed', 'failed').

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?

Only one parameter 'id' with an adequate schema description. The tool description adds no further meaning beyond 'Crawl job ID to check'. Schema coverage is 100%, so baseline 3 is appropriate.

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 states a specific verb 'check status' and resource 'crawl job'. It clearly distinguishes from siblings like firecrawl_crawl (initiates crawl) and firecrawl_scrape (single page scrape) by focusing on monitoring.

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?

No explicit guidance on when to use this tool versus alternatives. While context implies it's for polling after starting a crawl with firecrawl_crawl, the description does not state when not to use it or provide usage scenarios.

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

Deploy Server