Firecrawl MCP Server

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "firecrawl_monitor_list"
  }
}

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.
`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.6/5.0

Behavior4/5

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

The annotations already establish a read-only, nondestructive operation. Beyond that, the description usefully adds authenticated-account scope and discloses that each call returns only one page rather than the full collection, though it omits authentication prerequisites, pagination defaults, and empty-result behavior.

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-load the operation and account scope, then state the single-page behavior without filler. The wording is appropriately sized for a simple list tool.

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?

For a simple read operation with two optional parameters and an output schema, the account scope and single-page behavior cover most of what is needed to invoke it. Missing limit/offset semantics, pagination defaults, and sibling-selection guidance leave noticeable but not severe gaps.

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?

With 0% schema description coverage, the description needed to explain that limit caps the returned record count and offset skips records, along with any defaults or recommended values. "Optional pagination controls" only supplies a generic category and does not document either parameter individually.

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?

The description uses a specific verb and resource—"List monitors"—and narrows the scope to the authenticated account, while also clarifying that it retrieves a page of records. It does not explicitly distinguish this enumeration operation from firecrawl_monitor_get or firecrawl_monitor_checks, so it stops short of a 5.

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?

Enumerating an account's monitors and paging through them is implied by the wording, giving an agent basic usage context. There is no explicit when-to-use guidance or routing to firecrawl_monitor_get for a known monitor, or to other monitor tools for checks, runs, or modifications.

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