Skip to main content
Glama

Firecrawl by Nova (CIVAI)

firecrawl_monitor_check

Retrieve one monitor check and its page-level results, optionally filtered by page status. Pages report same, new, changed, removed, or error; configured goal judging can add a meaningful-change decision.

Markdown tracking returns a unified text diff, JSON tracking returns field paths with previous/current values and a current snapshot, and mixed tracking returns both. Returns one page of results plus a next URL when more pages exist.

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>",
      "checkId": "<checkId>"
    },
    "name": "firecrawl_monitor_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
skipNo
limitNo
checkIdYes
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.
pageStatusNo

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?

No annotations are supplied, so the description carries the full disclosure burden. It does well on output structure, explaining that markdown tracking returns a unified text diff, JSON returns field paths with previous/current values plus a snapshot, and mixed returns both, and it discloses pagination through a `next` URL. However, it never states that this is a read-only, non-mutating call, nor anything about permissions or rate limits, leaving meaningful behavioral gaps for an unannotated 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 paragraphs, front-loaded with the core action and then the output-shape detail, with essentially no filler. The only mild inefficiency is enumerating page statuses that the schema enum already lists.

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 six-parameter read tool with no output schema, the description does good work describing return shapes and pagination. It falls short on the required `id`/`checkId` identity semantics and on skip/limit paging behavior, which the schema does not cover, so an agent still guesses at parts of the call contract.

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?

Schema coverage is only 17%, so the description must compensate for the five undocumented parameters. It explains only the pageStatus values, and even that largely restates the schema enum, while `id`, `checkId`, `skip`, and `limit` are never mentioned. With most parameters undocumented in both schema and prose, the description leaves too much unexplained.

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 opens with a specific verb and resource: "Retrieve one monitor check and its page-level results." That is clearly distinct from firecrawl_monitor_list or firecrawl_monitor_checks, which would enumerate checks, but the definition never names a sibling to sharpen the boundary. An agent can identify the operation, though it must infer the difference from siblings by name alone.

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?

Usage is only implied: "optionally filtered by page status" suggests when the pageStatus filter is appropriate, but there is no explicit when-to-use statement, no prerequisites, and no statement of when to prefer firecrawl_monitor_checks or firecrawl_monitor_get instead. The reader is left to infer the appropriate context.

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