Skip to main content
Glama

Firecrawl by Nova (CIVAI)

firecrawl_agent_status

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.

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_agent_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
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.
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.

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. First observed

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does so well: it discloses the asynchronous/non-terminal state model, expected latency, terminal statuses, and what a completed response contains. It stops short of describing failure payloads or per-call rate limits, which keeps it from a 5.

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?

Front-loads purpose, then polling cadence and terminal conditions, then the fallback route, then return values — four short, dense sentences with no filler. Every sentence changes how the agent would call the tool.

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?

With no annotations and no output schema, the description must explain both async behavior and what comes back, and it does: status, progress, and result data on completion, plus the polling loop needed to reach that point. 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%; `objective` and `conversationId` are fully documented in the schema and need no help. The one gap is `id`, which has no schema description, and the description only indirectly supplies its meaning by tying it to a `firecrawl_agent` job ID. That is useful but not a full compensation, so baseline 3 fits.

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?

States a specific verb and resource — 'Retrieve progress or final results for a `firecrawl_agent` job ID' — which makes clear this is the polling companion to the firecrawl_agent job-starting tool. An agent can distinguish it from firecrawl_agent, firecrawl_check_crawl_status, and firecrawl_search without opening the schema.

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?

Gives explicit when-to-use semantics: poll every 15–30 seconds, `processing` is non-terminal, keep going until `completed` or `failed`, typical runtime 1–3 minutes. It also names the fallback path (firecrawl_search and firecrawl_scrape) when time runs out, which is exactly the alternative-selection guidance a polling tool needs.

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