Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

List Alert Events

list_alert_events
Read-only

Retrieve alert events for a specific alert ID using filters for status, source, labels, services, groups, environments, and time ranges to inspect alert activity.

Instructions

List alert_events

Input Schema

NameRequiredDescriptionDefault
includeNo
alert_idYesRequired. ID of the alert (fills `{alert_id}` in /v1/alerts/{alert_id}/events).
page_sizeNoNumber of results per page (max: 20)
filter_kindNo
page_numberNoPage number to retrieve
fields_alertsYesComma-separated list of alert fields to include (reduces payload size)id,summary,status,started_at,ended_at,short_id,alert_urgency_id,source,noise
filter_actionNo
filter_groupsNoFilter by team/group IDs (comma-separated)
filter_labelsNoFilter by labels (comma-separated)
filter_sourceNoFilter by alert source
filter_statusNoFilter by alert status (e.g., triggered, acknowledged, resolved)
filter_servicesNoFilter by service IDs (comma-separated)
filter_ended_at_gtNoEnded at > (ISO8601 datetime)
filter_ended_at_ltNoEnded at < (ISO8601 datetime)
filter_ended_at_gteNoEnded at >= (ISO8601 datetime)
filter_ended_at_lteNoEnded at <= (ISO8601 datetime)
filter_environmentsNoFilter by environment IDs (comma-separated)
filter_created_at_gtNoCreated at > (ISO8601 datetime)
filter_created_at_ltNoCreated at < (ISO8601 datetime)
filter_started_at_gtNoStarted at > (ISO8601 datetime)
filter_started_at_ltNoStarted at < (ISO8601 datetime)
filter_created_at_gteNoCreated at >= (ISO8601 datetime)
filter_created_at_lteNoCreated at <= (ISO8601 datetime)
filter_started_at_gteNoStarted at >= (ISO8601 datetime)
filter_started_at_lteNoStarted at <= (ISO8601 datetime)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.4.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond them — no note on pagination limits, payload behavior, filter interactions, or that results are scoped to one alert.

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

Conciseness2/5

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

At three words this is under-specification rather than conciseness. There is nothing to front-load because no substantive information is present.

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?

An output schema exists so return values need not be explained, but a 25-parameter filtered-list tool with three undocumented filter parameters deserves at least a sentence on scoping and filter semantics. The definition leaves the agent to infer everything from the schema.

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 88%, so the schema carries nearly all parameter meaning; a baseline of 3 applies. The description does not compensate for the few undocumented parameters (include, filter_kind, filter_action), which remain opaque.

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

Purpose2/5

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

The description restates the name and title verbatim ('List alert_events') without adding a specific scope, resource context, or sibling differentiation. An agent cannot tell from this text how it differs from sibling tools like list_alerts, get_alert_event, or list_incident_alerts.

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?

There is no when-to-use guidance, no mentioned alternatives, and no prerequisites. The only implied usage comes from the required alert_id parameter in the schema (events for a given alert), which the description does not surface.

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

Deploy Server

Other Tools