Update monitor
update_monitorModify an existing website monitor's name, check frequency, pause state, alert conditions, extraction rules, or pre-check actions; omitted fields stay unchanged.
Instructions
Update an existing monitor: rename, change frequency, pause/resume, or change its alert conditions, extraction and pre-check actions (requires a write-scope API key). Omitted fields stay unchanged; pass null to clear notifyWhen, notifyConditions, jsonPath, outputExtractorPattern, notifyWebhookUrl or actions.
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": {
"uuid": "<uuid>"
},
"name": "update_monitor"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | New monitor name | |
| uuid | Yes | Monitor uuid (from list_monitors) | |
| active | No | true resumes checks, false pauses them | |
| skills | No | Extra checks to run on the page at every check, each alerting on its own rules, on top of change monitoring: skill names from list_skills ('perf', 'seo', 'a11y', 'links', 'xss', 'tls', 'scripts', 'privacy', …) or plain words ('core web vitals', 'ssl', 'gdpr'). Add one only when the user asks for what it does. A skill the plan does not include is not added and comes back in skillsSkipped. Replaces the monitor's skills; pass null to remove them all. | |
| actions | No | Ordered list of interactions to perform before each check, e.g. [{"type":"CLICK","selector":"#accept-cookies"},{"type":"WAIT","value":1500},{"type":"CLICK","selector":".load-more"}]. Use this when the content to monitor is behind a cookie banner, a tab, a "show more" control, or a dropdown. Max 20 steps. Script and JS/CSS injection steps are dashboard-only and rejected here. Replaces the whole list; read the monitor first to keep existing steps. Pass null to remove them all. | |
| jsonPath | No | For JSON API endpoints: JSONPath to the value to monitor, e.g. $.data.items[0].price. Starts with '$'. Pass null to clear. | |
| keywords | No | TEXT monitors only: comma-separated keywords to look for, e.g. "sold out, unavailable" Pass null to clear. | |
| frequency | No | Minutes between checks, as a string: '5', '15', '30', '60' (hourly), '180', '360', '720', '1440' (daily), '10080' (weekly), '302400' (monthly). Omit for the plan default. A frequency faster than the plan allows is raised to the plan minimum. | |
| notifyWhen | No | Natural-language alert condition evaluated by AI on every check, e.g. 'notify me when the price drops below $500' or 'alert when the Pro plan changes'. Mutually exclusive with notifyConditions. Pass null to clear. | |
| skillAlerts | No | Alert rules per skill, only when the user names a threshold or a rule, e.g. {"perf": {"lcp": 3}}: a number sets the rule's threshold and turns it on (seconds for timings, MB for page weight, days for expiry, 0-100 for scores), true/false turns a rule on or off, null resets it. Rule ids are in list_skills. A skill named here is added to the monitor. Merged into the monitor's current rules. | |
| notifyEmails | No | Extra email addresses to CC on alerts (workspace members are emailed by default) Pass null to clear. | |
| keywordsAction | No | TEXT monitors only: alert when keywords are ADDED to the page (default) or REMOVED from it | |
| outputExtractor | No | How to extract the monitored value from the page text: NUMBER pulls the first number (good for prices), REGEX applies outputExtractorPattern, NONE keeps the full text. | |
| notifyConditions | No | Deterministic alert conditions on the extracted output (no AI credits). All conditions must pass. Requires the output to change. Mutually exclusive with notifyWhen. Not available for HTML monitors. Pass null to clear. | |
| notifyWebhookUrl | No | Webhook URL to POST alerts to (HMAC-signed with the account webhook secret) Pass null to clear. | |
| outputExtractorPattern | No | Regular expression for outputExtractor: REGEX — bare pattern or /pattern/flags; the first capture group (or full match) becomes the monitored output, e.g. 'In stock: (\d+)' Pass null to clear. |