Skip to main content
Glama

mcp-uptimerobot__list-monitors

Read-onlyIdempotent

List all monitors for the authenticated user. Third-party services are not listed here, use list-third-party-services for those. Through Royally: its server marks it read-only, so it runs straight away.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mcp-uptimerobot__list-monitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoCase-insensitive partial match on the monitor URL
nameNoCase-insensitive partial match on the monitor name (friendlyName)
tagsNoFilter monitors that carry any of these tag names
limitNoNumber of items to return per page (default: 10, max: 100)
cursorNoPagination cursor for next page
filterNoArray of monitor state filters. Possible values: PAUSED, STARTED, UP, LOOKS_DOWN, DOWN, EXPIRING_DOMAIN, EXPIRING_SSL_CERTIFICATE, WITH_API_KEY, WITHOUT_API_KEY
groupIdNoFilter monitors belonging to this monitor group id
site_idNoSite to run this tool on: 0b6d9b21-ca64-4476-bc68-d1cd935ca7cb (https://mcp.uptimerobot.com/mcp)
customFieldNoFilter monitors by custom field key:value pairs. Format: "key:value" per entry. Multiple entries use AND logic. Split on first colon only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the sentence about the server marking it read-only restates structured data rather than adding context. The one genuinely additive detail is the ownership scope ("for the authenticated user"), but pagination behavior (default page size, cursor paging) is left undisclosed even though it is the main behavioral surprise for this tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the sibling exclusion are correctly front-loaded, but the third sentence ("Through Royally: its server marks it read-only, so it runs straight away") is awkwardly worded and duplicates the annotations without paying rent. Two sentences would carry the same information.

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?

With nine parameters, no output schema, and pagination implied by limit/cursor, the description should signal that results are paged and that filtering is available. It covers scope and the tool boundary but leaves the agent to discover paging behavior from the schema alone.

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 all nine parameters including the enum-constrained filter and the customField key:value format are already documented in the schema. The description adds no syntax, default, or combination semantics beyond that, which is the expected baseline when the schema does the work.

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?

Uses a specific verb and resource ("List all monitors for the authenticated user") and explicitly separates itself from the closely-named sibling list-third-party-services, which is exactly the confusion an agent would otherwise have to resolve by opening both schemas.

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

Usage Guidelines4/5

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

Names the alternative tool and the condition that selects it (third-party services go to list-third-party-services), which is the highest-risk routing decision here. It gives no guidance on when to prefer get-monitor-details over this list, nor on when the filter/group/tag parameters should be used versus a broad listing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources