Skip to main content
Glama
84emllc

UptimeRobot MCP Server

by 84emllc

create_monitor

Create a new uptime monitor to watch a URL or IP, setting check intervals, timeouts, and alert contacts for availability tracking.

Instructions

Create a new monitor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL or IP address to monitor.
typeNoMonitor type. 1=HTTP(S), 2=Keyword, 3=Ping, 4=Port, 5=Heartbeat.
timeoutNoTimeout in seconds (1-300, default 30).
intervalNoCheck interval in seconds (60-2592000, default 300).
post_typeNoPOST body format: "raw" or "keyvalue".
post_valueNoPOST body content.
http_methodNoHTTP method for HTTP(S) monitors. 1=HEAD, 2=GET, 3=POST, 4=PUT, 5=PATCH, 6=DELETE, 7=OPTIONS.
keyword_typeNoRequired for Keyword monitors (type=2). 1=Keyword exists, 2=Keyword not exists.
friendly_nameYesDisplay name for the monitor.
keyword_valueNoThe keyword to search for. Required for type=2.
alert_contactsNoAlert contacts to attach, format "id_threshold_recurrence". Separate multiple contacts with "-". Example: "123_0_0-456_0_0".
http_auth_typeNoHTTP authentication type. 0=None, 1=Basic, 2=Digest.
http_auth_userNoUsername for HTTP authentication.
http_auth_secretNoCredential for HTTP authentication.
ignore_ssl_errorsNoWhether to ignore SSL certificate errors.
keyword_case_typeNo0=Case insensitive, 1=Case sensitive.
post_content_typeNoContent-Type header for POST requests. Options: "application/json", "application/x-www-form-urlencoded", "text/xml", "text/plain".
custom_http_headersNoJSON string of additional request headers. Example: '{"X-Custom-Header":"value"}'.
custom_http_statusesNoCustom HTTP status code mappings. Format: "200:1_201:1_404:0" where 1=up, 0=down.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Create a new monitor' without disclosing side effects, authentication requirements, or response behavior. This is insufficient for a mutation tool.

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 a single sentence with no filler. It is front-loaded and efficient, though minimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite the schema richness and output schema, the description provides almost no contextual information. It lacks any behavioral or usage context, making it inadequate for a complex 19-parameter tool.

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?

The schema provides detailed descriptions for all 19 parameters, so the baseline is 3. The description adds no parameter semantics beyond the schema, but it doesn't need to given the high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Create' and identifies the resource 'monitor', which clearly differentiates it from sibling tools like edit_monitor and delete_monitor. It is concise and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidance is provided. The description does not state when to use this tool versus alternatives, nor does it mention any prerequisites or context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/84emllc/uptimerobot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server