Firecrawl MCP Server

by firecrawl

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Get Firecrawl monitor

firecrawl_monitor_get

Read-only

Retrieve a monitor's configuration and current state by ID without running or modifying it.

Instructions

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

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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.2Oct 29, 2026

changedInput schema / $schema

Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "description": "One monitor record.",
+  "properties": {
+    "data": {
+      "description": "The monitor record: configuration, schedule, targets, and current state."
+    },
+    "error": {
+      "description": "Error message or error object when the call did not succeed."
+    },
+    "success": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Whether the API call succeeded."
+    }
+  },
+  "type": "object"
+}

First observedv1.0.1Jul 5, 2026

TDQS

A3.6/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 safety profile is fully covered. The description adds that the response includes configuration and current state and reaffirms no side effects, which is mild added context but not beyond what annotations imply.

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 verb and resource, with no redundant or filler content. The clarifying negative clause is worth its length.

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, so return details needn't be explained, and annotations cover the safety profile. For a one-parameter lookup tool the description is essentially sufficient, with only the lack of sibling routing as a remaining gap.

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 0%, so the 'id' parameter is undocumented structurally; the description only says 'by ID', which adds little beyond the property name and type. The single trivial parameter keeps the gap small.

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 ('Retrieve'), resource ('monitor'), and scope ('one ... by ID'), plus what is returned (configuration and current state). It implicitly separates itself from monitor_update/monitor_run via the negative clause, though it never names a sibling.

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 clause 'does not run or modify the monitor' signals a read-only fetch rather than monitor_run or monitor_update, which is useful exclusionary guidance. However, it doesn't state when to use this versus firecrawl_monitor_list or firecrawl_monitor_checks, leaving selection partly to inference.

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