Skip to main content
Glama

list_uptime_monitors

Retrieve uptime monitors by filtering on name, type, target, status, and more. Paginate results to get detailed insights including uptime, SSL, domain, and nameserver data.

Instructions

List uptime monitors with optional filters and pagination.

Returns a monitors array with detailed info: id, name, type, target, resolve_address, port, keyword, category, timeout, check_frequency, uptime_status, monitor_status, uptime%, locations, ssl info, domain info, nameservers, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo32-char monitor ID filter
nameNoFilter by monitor name
pageNoPage number
typeNoMonitor type: website, ping, service, smtp, or heartbeat
orderNoSort order: 'asc' or 'desc'
targetNoFilter by target URL/host
categoryNoFilter by category
order_byNoSort field: name, created_at, last_check, last_status_change, uptime_status, or monitor_status
per_pageNoResults per page
uptime_statusNo'up' or 'down'
monitor_statusNoactive, paused, disabled, maint, or maint_dnd

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the return shape (a monitors array with detailed fields) but does not explicitly state that the operation is read-only, lacks side effects, or requires any special permissions. The 'List' verb implies a safe read but this is not stated.

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?

The description is two sentences: the first states the action and general behavior, the second enumerates the return fields. It is front-loaded with the core purpose and avoids fluff. The second sentence is a long list but is still informative and earns its place, though it may overlap with the output schema.

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?

With 11 optional parameters, 100% schema coverage, and an output schema available, the description is sufficient for an agent to understand the tool's role. It lacks only explicit guidance on when to choose this over related tools and any edge-case behaviors like result limits, but overall it is complete for a list operation.

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 the baseline is 3. The description only mentions 'optional filters and pagination' without adding meaning beyond the schema's parameter descriptions. It does not explain parameter formats, dependencies, or defaults beyond what the schema already provides.

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 'List' with the resource 'uptime monitors' and explicitly mentions optional filters and pagination. It clearly distinguishes from sibling list tools (list_warning_policies, list_downtimes, etc.) by focusing on uptime monitors.

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?

The description provides clear context: it lists monitors with optional filters/pagination. However, it does not explicitly mention when to use this tool over alternatives (e.g., get_uptime_report for summaries) or any exclusion criteria.

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/khrns-r/hetrixmcp'

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