Skip to main content
Glama

Firecrawl by Nova (CIVAI)

firecrawl_monitor_run

Queue an immediate check for a monitor outside its normal schedule. This starts network work for the monitor's configured targets and returns the queued check.

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

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.

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

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that this kicks off real network work against the monitor's configured targets and that the result is a queued check rather than a completed result. It does not mention credit/cost implications, whether it can be run repeatedly or in parallel, or whether it needs any permissions, which matters for a triggering 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 tight sentences, front-loaded with the action and followed by the behavioral consequence. Nearly zero waste, though a short clause on the id parameter could have been added without bloat.

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 two-parameter trigger the coverage is borderline: the return value is addressed ('returns the queued check'), and the async nature is signaled, but the meaning of the required identifier and any preconditions for the monitor are left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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

At 50% schema coverage, the description should compensate for the undocumented parameter. It never clarifies that `id` is the monitor identifier (nor its expected format), and it says nothing about `objective`, which is only explained inside the schema itself.

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 ('Queue') and resource ('an immediate check for a monitor'), plus the distinguishing condition 'outside its normal schedule'. This differentiates an on-demand trigger from the retrieval-flavored siblings like firecrawl_monitor_check and firecrawl_monitor_checks, though no sibling is named explicitly.

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?

The phrase 'outside its normal schedule' implies when to use it (ad-hoc trigger vs. waiting for the scheduled run), but there is no explicit when-not guidance, no prerequisites (e.g., monitor must exist and be active), and no routing to related tools such as updating the schedule instead.

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