Firecrawl MCP Server

Get Firecrawl monitor

firecrawl_monitor_get

Read-only

Retrieve a monitor by ID to view its configuration and current state without running or modifying it. Use it to check monitor settings and status before making changes.

Instructions

Retrieve one monitor by ID, including its configuration and current state. This does not run or modify the monitor.

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

Input Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

Name	Required	Description
`data`	No	The monitor record: configuration, schedule, targets, and current state.
`error`	No	Error message or error object when the call did not succeed.
`success`	No	Whether the API call succeeded.
`agent_hints`	No	Optional response guidance from the Firecrawl API.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.28.2Nov 4, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the no-side-effects statement largely restates what structured data provides. The only added context is that the payload includes configuration and current state, with no mention of permissions, not-found behavior, or auth needs.

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?

Two short sentences, front-loaded with the action and scope, followed by the key exclusion. Nothing is redundant or padded.

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

Completeness4/5

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

An output schema exists and annotations carry the safety profile, so the description needn't explain return values. For a single-parameter read tool it is nearly sufficient; the remaining gap is how an agent obtains a valid monitor ID.

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?

With one parameter and 0% schema description coverage, the schema says only that 'id' is a required string. The description clarifies that it identifies a monitor, which is modest but real added meaning; it does not say where the ID comes from or its format.

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 ('Retrieve one monitor by ID') and scopes the result ('including its configuration and current state'). The singular 'one monitor' implicitly separates it from firecrawl_monitor_list, 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'This does not run or modify the monitor' is meaningful negative guidance that excludes the monitor_run and monitor_update siblings in a set where those are easy to confuse. It stops short of naming the alternatives or telling the agent to use firecrawl_monitor_list to discover IDs.

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