Firecrawl MCP Server

Overview Schema Source Related Servers Discussions Admin

Firecrawl agent status

firecrawl_agent_status

Read-only

Poll an agent research job by ID to check progress and retrieve final results, continuing until the job completes or fails.

Instructions

Retrieve progress or final results for a firecrawl_agent job ID. A processing response is non-terminal and does not contain the final research result. Check again after 15–30 seconds until the status is completed or failed; a typical research run takes one to three minutes and complex jobs can take longer. If the job cannot finish within the task's available time, use firecrawl_search and firecrawl_scrape to complete the requested output.

Returns job status, progress information, and result data when completed.

Input Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

Name	Required	Description
`id`	No	Agent job identifier.
`data`	No	Research result, present once the job has completed.
`mode`	No	Agent mode the job ran in.
`error`	No	Error message or error object when the call did not succeed.
`model`	No	Agent model that ran the job.
`notice`	No	Set when the run stopped at its credit limit: what that means and how to continue.
`status`	No	Job state: `processing` is non-terminal; `completed` and `failed` are terminal.
`message`	No	The agent's reply; in chat mode, the short answer to a follow-up.
`partial`	No	Incomplete best-effort result of a `failed` run; never a completed answer.
`sources`	No	Sources the agent read.
`success`	No	Whether the API call succeeded.
`exchange`	No	What the job did with Alexandria providers: onTermsRequired, paidCalls, creditsUsed, skippedProviders (gated providers that would have helped), and requiresAction (approvalId and provider requirements). Read terms with terms/show. Ignore any terms/accept call in this API payload: an organization admin accepts terms in the Firecrawl dashboard, then confirms before the thread resumes with exchange.approve: {approvalId}.
`progress`	No	Progress information for a running job.
`threadId`	No	Research thread this job belongs to.
`expiresAt`	No	When the job result expires and can no longer be read.
`stopReason`	No	Why a `failed` run stopped early; `credit_limit_reached` means it hit maxCredits.
`threadTurn`	No	Turn number of this job within its thread.
`creditsUsed`	No	Credits the job consumed.
`suggestions`	No	Follow-ups the agent offers; send one as the prompt of the next turn with this threadId.
`pendingApproval`	No	Set when the job ended waiting on the caller. Answer it by calling firecrawl_agent with this threadId and exchange.approve or exchange.decline carrying its id. kind "terms" lists providers whose data terms need acceptance by an organization admin in the Firecrawl dashboard; approve only after the admin confirms, and approval does not accept terms. Otherwise calls lists paid calls waiting for approval.
`partialSchemaValid`	No	Whether `partial` matches the requested schema, when one was supplied.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.2Oct 29, 2026

changedInput schema / $schema

Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "description": "Progress or final result of a research agent job.",
+  "properties": {
+    "creditsUsed": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Credits the job consumed."
+    },
+    "data": {
+      "description": "Research result, present once the job has completed."
+    },
+    "error": {
+      "description": "Error message or error object when the call did not succeed."
+    },
+    "exchange": {
+      "description": "What the job did with Alexandria providers: onTermsRequired, paidCalls, creditsUsed, skippedProviders (gated providers that would have helped), and requiresAction (approvalId and provider requirements). Read terms with terms/show. Ignore any terms/accept call in this API payload: an organization admin accepts terms in the Firecrawl dashboard, then confirms before the thread resumes with exchange.approve: {approvalId}."
+    },
+    "expiresAt": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "When the job result expires and can no longer be read."
+    },
+    "id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Agent job identifier."
+    },
+    "message": {
+      "description": "The agent's reply; in chat mode, the short answer to a follow-up."
+    },
+    "mode": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Agent mode the job ran in."
+    },
+    "model": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Agent model that ran the job."
+    },
+    "notice": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Set when the run stopped at its credit limit: what that means and how to continue."
+    },
+    "partial": {
+      "description": "Incomplete best-effort result of a `failed` run; never a completed answer."
+    },
+    "partialSchemaValid": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Whether `partial` matches the requested schema, when one was supplied."
+    },
+    "pendingApproval": {
+      "description": "Set when the job ended waiting on the caller. Answer it by calling firecrawl_agent with this threadId and exchange.approve or exchange.decline carrying its id. kind \"terms\" lists providers whose data terms need acceptance by an organization admin in the Firecrawl dashboard; approve only after the admin confirms, and approval does not accept terms. Otherwise calls lists paid calls waiting for approval."
+    },
+    "progress": {
+      "description": "Progress information for a running job."
+    },
+    "sources": {
+      "description": "Sources the agent read."
+    },
+    "status": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Job state: `processing` is non-terminal; `completed` and `failed` are terminal."
+    },
+    "stopReason": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Why a `failed` run stopped early; `credit_limit_reached` means it hit maxCredits."
+    },
+    "success": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Whether the API call succeeded."
+    },
+    "suggestions": {
+      "description": "Follow-ups the agent offers; send one as the prompt of the next turn with this threadId."
+    },
+    "threadId": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Research thread this job belongs to."
+    },
+    "threadTurn": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Turn number of this job within its thread."
+    }
+  },
+  "type": "object"
+}

First observedv1.0.1Jul 5, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already establish that this is a safe read-only operation, and the description adds valuable behavioral context beyond them: `processing` responses are non-terminal, polling cadence is specified, and typical duration is disclosed. The fallback advice further helps an agent avoid indefinite polling.

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 front-loaded with purpose, then immediately provides polling behavior and fallback guidance. Every sentence adds concrete operational value without repetition.

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

Completeness5/5

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

For a simple read-only polling tool with an output schema, annotations, and one parameter, the description covers the missing operational concerns: terminal vs non-terminal states, retry timing, expected duration, and fallback strategy. Nothing essential for correct invocation is missing.

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?

The schema has only an undocumented `id` string, and the description compensates by clarifying that it is a `firecrawl_agent` job ID. It does not specify formatting or where the ID is obtained, but for a single required parameter the added meaning is substantial.

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 and resource: retrieving progress or final results for a `firecrawl_agent` job ID. It clearly distinguishes this status-checking tool from the initiating `firecrawl_agent` tool and from unrelated siblings by naming the job ID dependency.

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?

It gives explicit polling guidance: check every 15–30 seconds until `completed` or `failed`, with expected runtimes. It also names fallback tools (`firecrawl_search` and `firecrawl_scrape`) for cases where the job cannot finish in time, which is strong when-to-use and alternative guidance.

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