Skip to main content
Glama
firecrawl

firecrawl-mcp-server

by firecrawl
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

firecrawl_agent_status

Read-only

Poll for agent job status and retrieve results when complete. Continue polling until status is 'completed' or 'failed'.

Instructions

Check the status of an agent job and retrieve results when complete. Use this to poll for results after starting an agent with firecrawl_agent.

IMPORTANT - Be patient with polling:

  • Poll every 15-30 seconds

  • Keep polling for at least 2-3 minutes before considering the request failed

  • Complex research can take 5+ minutes - do not give up early

  • Only stop polling when status is "completed" or "failed"

Usage Example:

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

Possible statuses:

  • processing: Agent is still researching - keep polling, do not give up

  • completed: Research finished - response includes the extracted data

  • failed: An error occurred (only stop polling on this status)

Returns: Status, progress, and results (if completed) of the agent job.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true, destructiveHint=false. Description adds polling behavior, statuses, and patience advice without contradiction.

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?

Well-structured with sections, example JSON, list of statuses. Detailed yet concise, every sentence adds value.

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?

Covers polling strategy, status meanings, result retrieval. No output schema but describes return types. Complete for a status polling tool.

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?

Only one parameter `id` with no schema description. Description mentions 'id' is from firecrawl_agent, which is adequate context. Could specify format but not necessary.

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?

Explicitly states it checks status of agent job and retrieves results. Clearly distinguishes from sibling `firecrawl_agent` which starts the agent.

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?

Provides detailed polling instructions: interval 15-30s, minimum 2-3 minutes patience, stop only on 'completed' or 'failed'. Explains when to use (after starting agent).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/firecrawl/firecrawl-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server