CatchAll

Update Monitor

update_monitor

Update a monitor's schedule, timezone, webhook assignments, and per-run limit.

Note: reference_job_id cannot be modified through this endpoint. Webhooks are centralized — pass webhook IDs (from create_webhook/list_webhooks).

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": {
      "monitor_id": "<monitor_id>"
    },
    "name": "update_monitor"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Optional updated maximum records per run (minimum 10).
`api_key`	No	CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var.
`schedule`	No	Optional new natural-language schedule to replace the monitor's current one (e.g. 'every day at 9 AM', 'every Monday at 6 PM EST'). Leave unset to keep the current schedule. The scheduler picks up the new schedule on its next reload and the old schedule stops firing.
`timezone`	No	Optional IANA timezone for the new schedule (e.g. 'America/New_York'). Defaults to UTC. Overridden if the schedule text itself contains a timezone. Ignored if `schedule` is not set.
`monitor_id`	Yes	The monitor ID to update
`webhook_ids`	No	Optional list of webhook IDs to assign to this monitor. Pass an empty list `[]` to clear all webhook assignments.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 22, 2026

addedInput schema / properties / schedule

Added value: +{
+  "default": "",
+  "description": "Optional new natural-language schedule to replace the monitor's current\none (e.g. 'every day at 9 AM', 'every Monday at 6 PM EST'). Leave unset to keep\nthe current schedule. The scheduler picks up the new schedule on its next\nreload and the old schedule stops firing.",
+  "type": "string"
+}

addedInput schema / properties / timezone

Added value: +{
+  "default": "",
+  "description": "Optional IANA timezone for the new schedule (e.g. 'America/New_York').\nDefaults to UTC. Overridden if the schedule text itself contains a timezone.\nIgnored if `schedule` is not set.",
+  "type": "string"
+}

First observedJul 14, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one behavioral limitation (reference_job_id cannot be modified) and clarifies that webhooks are centralized, which adds context beyond the schema. However, it does not mention side effects, reversibility, permissions, or whether the update is partial or full. This is partial transparency, warranting a 3.

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?

The description is extremely concise—two sentences plus a short note—and front-loads the core purpose. Every sentence adds value, and there is no redundant or filler content. This is a model of efficient, structured description.

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?

Given the tool's complexity (6 parameters, mutation, no annotations), the description covers the key purpose and notes the main limitation (reference_job_id) and webhook handling. However, it omits behavioral details like whether the update is partial or replaces all fields, and it does not address permissions or idempotency. Since an output schema exists and schema coverage is full, the return format is not needed, but the behavioral gaps prevent a higher score.

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 100%, so the baseline is 3. The description lists the updated fields (schedule, timezone, webhook assignments, per-run limit) which map to schema parameters, and the webhook note adds practical guidance. However, it does not add meaning beyond what the schema already provides for individual parameters, so no higher score is justified.

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 states a specific verb ('Update') and the resource ('a monitor') and enumerates the exact fields it affects (schedule, timezone, webhook assignments, per-run limit). This is clear and unambiguous, but it does not explicitly distinguish it from sibling tools like enable_monitor or disable_monitor, though its update semantics are evident.

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 description implies usage by the nature of an 'update' tool, but it provides no explicit guidance on when to use it versus alternatives (e.g., create_monitor for new monitors, disable_monitor for toggling state). The only guidance is a limitation note about reference_job_id, which is not about usage scenarios. This falls under 'implied usage' rather than explicit when/when-not guidance.

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

All CatchAll tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.