Skip to main content
Glama

Update monitor

update_monitor

Modify 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

NameRequiredDescriptionDefault
nameNoNew monitor name
uuidYesMonitor uuid (from list_monitors)
activeNotrue resumes checks, false pauses them
skillsNoExtra 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.
actionsNoOrdered 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.
jsonPathNoFor JSON API endpoints: JSONPath to the value to monitor, e.g. $.data.items[0].price. Starts with '$'. Pass null to clear.
keywordsNoTEXT monitors only: comma-separated keywords to look for, e.g. "sold out, unavailable" Pass null to clear.
frequencyNoMinutes 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.
notifyWhenNoNatural-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.
skillAlertsNoAlert 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.
notifyEmailsNoExtra email addresses to CC on alerts (workspace members are emailed by default) Pass null to clear.
keywordsActionNoTEXT monitors only: alert when keywords are ADDED to the page (default) or REMOVED from it
outputExtractorNoHow 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.
notifyConditionsNoDeterministic 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.
notifyWebhookUrlNoWebhook URL to POST alerts to (HMAC-signed with the account webhook secret) Pass null to clear.
outputExtractorPatternNoRegular 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses the auth requirement (write-scope API key), PATCH-style merge semantics (omitted fields unchanged), and that passing null clears specific fields — exactly the destructive-scope information an agent needs. It stops short of stating whether updates are reversible or what validation errors look like.

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 sentences, front-loaded with the action and scope; the second sentence carries the important partial-update rule. The trailing enumeration of nullable fields is somewhat listy but each item conveys real clearing behavior.

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?

Given 16 parameters, nested objects (skills, actions, skillAlerts) and no annotations or output schema, the description covers the overall shape and the state-merge/clear rules well. The complex nested parameters are left entirely to the schema, which is dense but complete at 100% coverage.

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 per-field meaning is already documented and the baseline is 3. The description adds genuinely useful cross-parameter semantics — 'omitted fields stay unchanged' and the enumerated null-clearing list — but the latter largely restates per-field 'Pass null to clear' notes already in the schema.

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 (update) plus the concrete operations the tool covers — rename, frequency, pause/resume, alert conditions, extraction and pre-check actions — so the agent knows exactly what it mutates. It does not distinguish itself from siblings like pause_monitor/resume_monitor, which overlap with the 'pause/resume' capability mentioned here.

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 context is implied by 'Update an existing monitor' and the prerequisite 'requires a write-scope API key', and the partial-update rule ('omitted fields stay unchanged') tells the agent how to call it. However, there is no explicit when-to-use/when-not guidance versus create_monitor, pause_monitor, resume_monitor, or delete_monitor, which an agent must infer.

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