Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

List Alerts

list_alerts
Read-only

Retrieve, filter, and paginate Rootly alerts with selected fields and related metadata to inspect incident signals and on-call activity.

Instructions

List alerts

Input Schema

NameRequiredDescriptionDefault
includeNocomma separated if needed. eg: environments,services,groups
page_sizeNoNumber of results per page (max: 20)
page_afterNoThe cursor to fetch results using cursor pagination. A cursor is provided in meta.next_cursor in the response.
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_groupsNo
filter_labelsNo
filter_sourceNo
filter_statusNo
filter_servicesNo
filter_groups_eqNo
filter_groups_inNo
filter_labels_eqNo
filter_labels_inNo
filter_source_eqNo
filter_source_inNo
filter_status_eqNo
filter_status_inNo
filter_ended_at_gtNo
filter_ended_at_ltNo
filter_services_eqNo
filter_services_inNo
filter_ended_at_gteNo
filter_ended_at_lteNo
filter_environmentsNo
filter_created_at_gtNo
filter_created_at_ltNo
filter_groups_not_eqNo
filter_groups_not_inNo
filter_labels_not_eqNo
filter_labels_not_inNo
filter_source_not_eqNo
filter_source_not_inNo
filter_started_at_gtNo
filter_started_at_ltNo
filter_status_not_eqNo
filter_status_not_inNo
filter_updated_at_gtNo
filter_updated_at_ltNo
filter_created_at_gteNo
filter_created_at_lteNo
filter_started_at_gteNo
filter_started_at_lteNo
filter_updated_at_gteNo
filter_updated_at_lteNo
filter_environments_eqNo
filter_environments_inNo
filter_services_not_eqNo
filter_services_not_inNo
filter_environments_not_eqNo
filter_environments_not_inNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.4.0

TDQS

D1.8/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 no behavioral context such as pagination behavior, filter semantics, default ordering, or the effect of the many filter parameters. It does not contradict the annotations.

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?

The description is extremely short, but this is under-specification rather than useful conciseness. It is front-loaded only in the sense that it has nothing to front-load.

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

Completeness1/5

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

For a tool with 51 parameters, 1 required field, and many undocumented filters, a two-word description is completely inadequate. Even though an output schema exists, the description should explain the filtering model and pagination approach that the sparse schema does not cover.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 51 parameters and only 10% schema description coverage, the description must compensate but provides zero parameter information. Most filter_* parameters have no schema descriptions, so an agent has no explanation of their semantics from either the schema or the description.

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?

Tautological: description restates name/title.

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?

The description provides no guidance on when to use this tool versus alternatives like list_incident_alerts, list_alert_events, or get_alert_by_short_id. There are also no prerequisites, exclusions, or context cues to help with tool selection.

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