Firecrawl MCP Server

Overview Schema Source Related Servers Discussions Admin

List Firecrawl monitors

firecrawl_monitor_list

Read-only

List monitors for the authenticated account with optional limit and offset pagination, returning one page of monitor records plus pagination metadata.

Instructions

List monitors for the authenticated account with optional pagination controls. Returns one page of monitor records and pagination metadata.

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No

Output Schema

Name	Required	Description
`data`	No	One page of monitor records.
`error`	No	Error message or error object when the call did not succeed.
`success`	No	Whether the API call succeeded.
`pagination`	No	Pagination metadata for the listing.

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 page of monitors for the authenticated account.",
+  "properties": {
+    "data": {
+      "description": "One page of monitor records."
+    },
+    "error": {
+      "description": "Error message or error object when the call did not succeed."
+    },
+    "pagination": {
+      "description": "Pagination metadata for the listing."
+    },
+    "success": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Whether the API call succeeded."
+    }
+  },
+  "type": "object"
+}

First observedv1.0.1Jul 5, 2026

TDQS

B3.4/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 safety is covered. The description adds account scoping and that results are a single page with pagination metadata, but omits ordering, default limit, and total-count semantics.

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 short sentences, front-loaded with the core operation and followed by return-shape context. No filler, though the second sentence partially duplicates what the output schema already conveys.

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?

An output schema exists, so return values needn't be spelled out, and the description correctly signals paging. What's missing is pagination mechanics (defaults, max limit, how to detect more pages) — important for a tool whose only parameters are pagination controls.

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 description must carry the load for limit and offset. It only gestures at 'optional pagination controls' without defining default limit, maximum page size, or offset behavior, leaving the agent to guess.

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 ('List monitors for the authenticated account') and scopes it to the caller's account. An agent can distinguish it from firecrawl_monitor_get (single monitor) by inference, but the description never names that sibling 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?

Implies usage by saying it returns 'one page' with optional pagination controls, which hints at iteration. However, it never says when to prefer this over firecrawl_monitor_get or firecrawl_monitor_checks, and gives no guidance on default page size or how to paginate further.

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