> ## Documentation Index
> Fetch the complete documentation index at: https://docs.particle.pro/llms.txt
> Use this file to discover all available pages before exploring further.

# particle_alert_get

> Fetch a single alert's full configuration, optionally with recent matches and deliveries.

Fetch a single alert's full configuration — title, kind, cadence, watched entities (with names), notification emails, and any active filters (`languages`, `relevance`, `source_popularity`, `speaker_roles` — see [`particle_alert_create`'s filter object](/mcp/tools/alerts/alert-create#filter-object)). The `filters` section is omitted when the alert carries none. Read-only.

The default response is just the configuration. It is **lean by default and expands**: request `include=["matches"]` to embed the most recent matches the alert has caught, and `include=["deliveries"]` for the email delivery audit log. For the full, paginated match history with transcript excerpts, use [`particle_alert_list_matches`](/mcp/tools/alerts/alert-list-matches).

## Inputs

| Field         | Type           | Required | Default | Description                                                                                                                                                                        |
| ------------- | -------------- | -------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `alert_id`    | string         | yes      | —       | Alert id from [`particle_alert_list`](/mcp/tools/alerts/alert-list) or [`particle_alert_create`](/mcp/tools/alerts/alert-create).                                                  |
| `include`     | array of enums | no       | `[]`    | Optional sections to embed: `matches` (the most recent matches the alert has caught), `deliveries` (the email delivery audit log).                                                 |
| `match_limit` | integer (1–25) | no       | 5       | How many recent matches to embed when `include=["matches"]`. Use [`particle_alert_list_matches`](/mcp/tools/alerts/alert-list-matches) for full pagination and transcript windows. |

## Output

A markdown document with the alert configuration (same shape as [`particle_alert_create`](/mcp/tools/alerts/alert-create)): the title as an H2, `**ID:**`, `**Kind:**`, `**Delivery:**`, `**Status:**` rows, an optional `**Description:**` row, a `### Watching (N)` entity list, a `**Notify:**` row, and (when any filter is set) a `### Filters` section with one bullet per configured axis.

When requested, a `### Recent matches (N)` section embeds each match as a bullet naming the episode and mention count (with the episode slug), and a `### Recent deliveries (N)` section lists each delivery as `\`id\` · channel · status · N matches\`.

Sample (`alert_id="dKxN6Ry2mL9pJ5qW", include=["matches"]`):

```markdown theme={"dark"}
## OpenAI mentions

**ID:** dKxN6Ry2mL9pJ5qW
**Kind:** ENTITY_MENTION
**Delivery:** DAILY
**Status:** active

### Watching (1)

- **Sam Altman:** PERSON · 9rQ2pV…

- **Notify:** you@example.com

### Recent matches (2)

- The AI Daily (Acme Network) — 3 mentions
  - **Episode:** the-ai-daily-2026-06-15
- Tech Roundup — 1 mention (backfilled)
  - **Episode:** tech-roundup-ep-204
```

Passing `output_format: "json"` returns the same fields (plus `matches`/`deliveries`) as compact JSON.

## Example

```text theme={"dark"}
Agent calls: particle_alert_get {
  "alert_id": "dKxN6Ry2mL9pJ5qW",
  "include": ["matches", "deliveries"]
}
```

## Related

* REST equivalent: [`GET /v1/alerts/{id}`](/api-reference/alerts/get-an-alert).
* For the full, paginated match history with transcript windows, use [`particle_alert_list_matches`](/mcp/tools/alerts/alert-list-matches).
* Update or pause the alert with [`particle_alert_update`](/mcp/tools/alerts/alert-update); remove it with [`particle_alert_delete`](/mcp/tools/alerts/alert-delete).