AlertOps MCP Server

alertops_list_alerts

Retrieve alerts with filters for status, date ranges, alert ID, group, integration, or escalation rules. Supports pagination, newest first, and returns IDs usable for follow-up.

Instructions

List alerts, newest first by default. Filter by status (open/closed/assigned/all), a date range (created or closed), a specific AlertID, or by group/integration/escalation-rule IDs. Paginated (Limit, max 100 per page; Offset). AlertIDs from this response are usable directly; message-level lookups (by inbound integration's messageID or uniqueInboundID) are separate tools.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Page size. Default 10, max 100.
`order`	No	'desc' (default) or 'asc', by created date.
`offset`	No	Starting point for the result set. Default 0.
`date_to`	No	Created-date upper bound, format 'yyyy-mm-dd'.
`alert_id`	No	Return only this AlertID.
`date_from`	No	Created-date lower bound, format 'yyyy-mm-dd'.
`group_list`	No	Comma-separated Group IDs to filter by, e.g. "123,456". From alertops_list_groups.
`alert_status`	No	Open=1, Closed=2, Assigned=5, All=0. Default 0 (all).
`closed_to_date`	No	Closed-date upper bound, format 'yyyy-mm-dd'.
`escalation_list`	No	Comma-separated Escalation Rule IDs to filter by, e.g. "123,456".
`closed_from_date`	No	Closed-date lower bound, format 'yyyy-mm-dd'.
`integration_list`	No	Comma-separated Integration Rule IDs to filter by, e.g. "123,456". From alertops_list_integrations.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses default sort order, pagination limits, filter behavior, and the direct usability of returned AlertIDs. It does not describe the return payload shape or rate limits, but for a read-only list operation this is a solid disclosure.

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

Conciseness5/5

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

Three dense, front-loaded sentences cover behavior, filters, pagination, and sibling differentiation with no filler. Every sentence earns its place.

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 12-parameter tool with no required parameters and no annotations, the description covers all major filter groups, pagination semantics, and sibling boundaries. It is slightly shy of perfect because there is no output schema and the description does not describe the shape of the returned alert list, though that is not essential for invocation.

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 structured schema already documents every parameter. The description adds useful grouping (status, created/closed dates, group/integration/escalation IDs, pagination) but no significant per-parameter meaning beyond what the schema 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 states the exact operation ('List alerts'), the default ordering ('newest first by default'), and enumerates all filter dimensions. It also draws a clear boundary against message-level lookup siblings, so an agent can distinguish this tool from alertops_get_alert_id_by_* immediately.

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?

It specifies the main use case (listing/filtering alerts with pagination) and explicitly warns that message-level lookups by messageID/uniqueInboundID are separate tools. It does not name those sibling tools or give an explicit 'use X when' statement, but the context is clear.

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

Deploy Server

alertops_list_alerts

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools