Skip to main content
Glama

mcp-uptimerobot__list-integrations

Read-onlyIdempotent

List all integrations for the authenticated user. Personal alert contacts (email, Pro SMS, voice, iOS/Android push) are a separate resource, read via list-alert-contacts. 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-integrations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return per page (default: 10, max: 100)
cursorNoPagination cursor for next page
site_idNoSite to run this tool on: 0b6d9b21-ca64-4476-bc68-d1cd935ca7cb (https://mcp.uptimerobot.com/mcp)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The sentence "its server marks it read-only, so it runs straight away" largely restates readOnlyHint rather than adding new behavior, and nothing is said about pagination or result shape. Some credit for confirming no approval step is needed, but it is mostly redundant.

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 first two sentences are front-loaded and earn their place, cleanly separating integrations from alert contacts. The third sentence is filler that repeats the readOnlyHint annotation and introduces a "Through Royally" reference that adds no actionable information for the caller.

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?

For a simple read-only list tool with no output schema and fully documented parameters, the description covers identity, scope, and the most likely routing mistake. Only minor gaps remain around result ordering and pagination behavior, which the schema partially covers.

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%, with limit, cursor, and site_id all documented inline, so the schema carries parameter meaning on its own. The description adds no clarification about pagination or the site_id enum, which is the appropriate baseline for a fully documented schema.

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?

States a specific verb and resource ("List all integrations for the authenticated user") and immediately scopes it by naming the adjacent resource it does not cover. An agent can distinguish it from list-alert-contacts without reading either schema.

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?

Provides an explicit exclusion and names the correct alternative (list-alert-contacts) for personal alert contacts, which is exactly the confusion an agent would hit here. It lacks positive guidance on when to reach for integrations (e.g., to find webhook/Slack endpoints to attach to a monitor), so it stops short of full when/when-not guidance.

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