Skip to main content
Glama

Update Monitor Tool

update-monitor

Update a monitor by ID. Supports HTTP, keyword, TCP, ping, and DNS monitors. Requires Full Access MCP token and eligible paid plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL to monitor for http and keyword monitors
hostNoHostname or IP for tcp, ping, and dns monitors
nameNoMonitor display name
portNoTCP port number 1-65535 for tcp monitors
typeNoType of check: http, keyword, tcp, ping, dns, or heartbeat (Pro+, passive inbound check-in)
keywordNoKeyword to search for keyword monitors
timeoutNoTimeout in seconds: 15, 30, or 60
monitor_idYesThe UUID of the monitor to update
monitor_sslNoEnable SSL certificate monitoring for http/keyword monitors
keyword_typeNoAlert when keyword exists or does not exist
notify_uptimeNoEnable uptime/recovery notifications
check_intervalNoFrequency of checks in seconds
monitor_domainNoEnable domain expiry monitoring for http/keyword monitors
alert_thresholdNoConsecutive failures before alerting: 1, 2, 3, or 5
dns_record_typeNoDNS record type for dns monitors
request_headersNoOptional HTTP request headers as objects with name and value
dns_expected_valueNoExpected DNS value for hijacking detection
monitor_page_speedNoEnable Page Speed monitoring when allowed by plan
pinned_region_codeNoLocation this monitor is checked from. Use list-check-regions for valid values; omit or send an empty string for automatic selection.
private_location_idNoUUID of one of your own Private Locations to check this monitor from instead of the Baromio fleet. Use list-private-locations for valid values. Only http, keyword, and tcp types are eligible.
accepted_status_codesNoHTTP monitors only: status codes 400-599 (at most 10) to count as up in addition to 200-399, for a URL that answers 401, 404 or 503 on purpose. Send an empty array to clear the list. Not available for keyword monitors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / accepted_status_codes
      Added value: +{
      +  "description": "HTTP monitors only: status codes 400-599 (at most 10) to count as up in addition to 200-399, for a URL that answers 401, 404 or 503 on purpose. Send an empty array to clear the list. Not available for keyword monitors.",
      +  "items": {
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / private_location_id
      Added value: +{
      +  "description": "UUID of one of your own Private Locations to check this monitor from instead of the Baromio fleet. Use list-private-locations for valid values. Only http, keyword, and tcp types are eligible.",
      +  "type": "string"
      +}
  3. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources