Firecrawl by Nova (CIVAI)

firecrawl_agent_activity

Read the live progress of a firecrawl_agent job for the Firecrawl agent view: its steps, searches, pages read and credits so far, and the result once it finishes. Used by the agent view; use firecrawl_agent_status to read a job.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Agent job ID from firecrawl_agent.
`event`	No	Records this action taken in the agent view, for usage counts, instead of reading the job.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

addedInput schema / properties / event

Added value: +{
+  "description": "Records this action taken in the agent view, for usage counts, instead of reading the job.",
+  "enum": [
+    "copy_result",
+    "download_csv",
+    "download_json",
+    "view_preview",
+    "view_table",
+    "page",
+    "retry",
+    "expand_steps",
+    "collapse_steps",
+    "show_earlier_steps",
+    "open_source",
+    "show_more_sources",
+    "open_result_link",
+    "expand_text",
+    "show_more_items"
+  ],
+  "type": "string"
+}

AddedNov 6, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It adds useful behavior ('live progress', 'the result once it finishes', credits accrued), but omits that passing the `event` parameter turns this into a usage-recording call with side effects rather than a read — a material behavioral trait for an unannotated tool.

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?

Two compact sentences with the returned data front-loaded; nothing is padded. The second sentence is slightly self-undermining ('use firecrawl_agent_status to read a job') without clarifying the distinction, which costs a point.

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?

With no annotations and no output schema, the description should explain the dual read/record mode and the shape of progress data, but it only partially does so. It does note that the final result appears only after completion, which is helpful, but the `event`-driven side-effect path is left entirely to the schema.

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 description coverage is 100% and the enum values are all documented in the schema, so the baseline of 3 applies. The description adds no meaning about the required `id` or the `event` mode switch beyond what structured fields already provide.

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: 'Read the live progress of a firecrawl_agent job', and enumerates what is returned (steps, searches, pages read, credits, final result). It names the sibling firecrawl_agent_status, so an agent can separate them, though the exact basis of separation (agent-view streaming vs. programmatic status polling) is only implied.

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?

It names the alternative ('use firecrawl_agent_status to read a job') but the guidance is confusing rather than decisive, since both tools ostensibly read a job. There is no explicit statement of when this tool is the right choice versus when status is, leaving the agent to infer agent-view UI context.

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

All Firecrawl by Nova (CIVAI) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?