Skip to main content
Glama

Firecrawl by Nova (CIVAI)

firecrawl_monitor_update

Patch an existing monitor by ID; changes affect future scheduled checks. Pause or resume it with status ("paused" or "active"). Reschedule it with scheduleText (plain language, e.g. "every 6 hours") or cron, plus timezone; a new schedule without timezone runs in UTC. For other fields pass body, a partial monitor in the create shape (name, targets, goal, judgeEnabled, webhook, notification, retentionDays), e.g. {"name": "Pricing watch"}. The parameters are merged into body as {"status": ..., "schedule": {"text" or "cron": ..., "timezone": ...}} and override the same keys there. At least one change is required.

Returns the updated 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_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
bodyNo
cronNo
statusNo
timezoneNo
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.
scheduleTextNo

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. Changed5 schema fields changed
    • addedInput schema / properties / cron
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / scheduleText
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / status
      Added value: +{
      +  "enum": [
      +    "active",
      +    "paused"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / timezone
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "id",
      -  "body"
      -]New value: +[
      +  "id"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / body / additionalProperties
      Previous value: -{}New value: +true
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden well: it discloses that the change is a partial merge, that direct parameters override the same keys inside `body`, that a schedule without `timezone` defaults to UTC, and that at least one change is mandatory. It omits permission/auth requirements and failure behavior, keeping it short of a 5.

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?

Front-loads the core action, then walks through the parameter modes in the order an agent would need them, ending with the return value. Sentences are dense but each carries distinct operational information; no filler.

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 7-parameter mutation tool with a nested `body`, no annotations, and no output schema, the description covers merge semantics, defaults, mutation scope, and the return value ("Returns the updated monitor"). The only meaningful omission is guidance on the `objective` parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 14%, so the description must compensate, and it largely does: it defines the `status` enum values, the plain-language form of `scheduleText`, the `cron` alternative, the UTC default for `timezone`, and enumerates the fields accepted through the opaque `body` object with a worked example. The `objective` parameter is never mentioned, which is a real gap for a 7-parameter tool.

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 ("Patch an existing monitor by ID") and adds the scope of effect ("changes affect future scheduled checks"). An agent can distinguish it from firecrawl_monitor_create or firecrawl_monitor_get without inspecting schemas, 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?

Gives concrete routing rules for the three usage modes: `status` for pause/resume, `scheduleText`/`cron`+`timezone` for rescheduling, `body` for everything else. It also states the precondition that at least one change is required. It does not explicitly point to an alternative tool (e.g., create vs. update) for ambiguous cases.

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