Skip to main content
Glama

mcp-uptimerobot__get-incident-activity-log

Read-onlyIdempotent

Read what happened during an incident: a summary (entry counts by kind, the contacts involved, the most recent entry) followed by the newest page of entries. Answers "what happened, and who was alerted?" in one call even on an incident with thousands of notifications. Recipient values are shown in full only for identifier-shaped contact types (email, SMS, voice); every other type is "[REDACTED]". Not for third-party service incidents, use get-third-party-service-incident-activity-log for those. Through Royally: its server marks it read-only, so it runs straight away.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "incidentId": "<incidentId>"
    },
    "name": "mcp-uptimerobot__get-incident-activity-log"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of notification entries per page (1-200, default 50). The first page also carries every comment and status update on top of those, so it can hold more than `limit` entries.
cursorNoPagination cursor for the next page of notification entries. Comments and status updates are only returned on the first page.
site_idNoSite to run this tool on: 0b6d9b21-ca64-4476-bc68-d1cd935ca7cb (https://mcp.uptimerobot.com/mcp)
incidentIdYesIncident ID (a BigInt value, passed as a numeric string)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, but the description adds behavior those annotations cannot express: recipient values are fully shown only for email/SMS/voice and are '[REDACTED]' otherwise, and the response is a summary plus the newest page rather than the full history. These are material disclosure details an agent must know before interpreting results.

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 dense and front-loaded, with the purpose and return shape first, then redaction semantics, then the exclusion, then deployment notes. The closing sentence about running read-only through Royally is partly redundant with the readOnlyHint annotation, keeping it short of a 5.

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

Completeness5/5

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

With no output schema, the description carries the burden of describing return values, and it does so thoroughly: summary composition, newest page of entries, and redaction rules. Combined with the explicit sibling exclusion, an agent has everything needed to call and interpret this tool correctly.

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 coverage is 100%, so limit, cursor, incidentId and site_id are already documented in the schema, including the note that the first page also carries comments and status updates. The description reinforces the paging/summary model but adds no new syntax or format detail beyond what the schema states, so the baseline 3 applies.

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 opens with a specific verb and resource ('Read what happened during an incident') and immediately specifies the return shape: a summary of entries by kind, involved contacts, most recent entry, plus the newest page. It also names the sibling it is not (get-third-party-service-incident-activity-log), so an agent can distinguish it without opening 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 Guidelines5/5

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

It states explicitly when not to use it ('Not for third-party service incidents') and names the replacement tool. The framing question 'what happened, and who was alerted?' and the 'even on an incident with thousands of notifications' note clarify the intended use case.

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