---
title: "list_alert_definitions"
description: "List alert definitions configured on the Kapptivate platform."
sidebarTitle: "list_alert_definitions"
lastUpdated: "2026-09-23"
---

> **For AI agents:** the complete documentation index is at [llms.txt](/llms.txt). Append `.md` to any page URL for its markdown version.

{/* GENERATED FILE: do not edit by hand. Regenerate with: node scripts/generate.mjs */}

List alert definitions configured on the Kapptivate platform.

<Note>
  **Read-only · Calls external systems.** Safe to call: this tool does not modify data.
</Note>

## Parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `archived` | string | No | Filter by archived status: true or false |
| `detail` | boolean | No | Return full JSON instead of compact summaries (default: false) |
| `name` | string | No | Filter by alert name |
| `operator` | string | Yes | Operator slug |
| `types` | string | No | Comma-separated alert types: raw_alert, availability, metric, agent_availability, availability_last_point |

## Example arguments

Illustrative arguments an agent supplies when calling this tool:

```json
{
  "operator": "string"
}
```

## Description

```text
These are persistent rules that automatically trigger incidents when conditions are met.

NOT the same as evaluate_alert which performs on-demand local analytics computation. To check platform alert status, use list_incidents.

Filters: name, types (comma-sep: raw_alert, availability, metric, agent_availability, availability_last_point), archived (bool).
```

## Related

- [`evaluate_alert`](/mcp/tools/metrics/evaluate_alert)
- [`list_incidents`](/mcp/tools/alerting/list_incidents)

## What's next?

<Columns cols={2}>
  <Card title="All MCP tools" icon="robot" href="/mcp/tools/overview">
    Browse the full tool reference by category.
  </Card>
  <Card title="Connect a client" icon="plug" href="/mcp/connect">
    Point Claude, Cursor, or Claude Code at the server.
  </Card>
</Columns>