> ## 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_list

> List the alerts in your project, newest first.

List the alerts in your project, newest first. Read-only. Every MCP request is scoped to one project by your credential, so this lists **that** project's alerts — there is no project parameter and no way to reach another project's alerts.

Each entry carries the alert `id` — feed it into [`particle_alert_get`](/mcp/tools/alerts/alert-get) for full configuration, [`particle_alert_list_matches`](/mcp/tools/alerts/alert-list-matches) for what it has caught, or [`particle_alert_update`](/mcp/tools/alerts/alert-update) / [`particle_alert_delete`](/mcp/tools/alerts/alert-delete) to manage it. Results are cursor-paginated.

## Inputs

| Field    | Type            | Required | Default | Description                                                         |
| -------- | --------------- | -------- | ------- | ------------------------------------------------------------------- |
| `limit`  | integer (1–100) | no       | 25      | Alerts per page.                                                    |
| `cursor` | string          | no       | —       | Opaque pagination cursor from a previous response's `cursor` field. |

## Output

A markdown `## Alerts (N)` heading followed by one bullet per alert: `Title — \`id\` · kind · cadence · N entities`, with a nested `**Status:**`row (active/paused). When more results remain, a trailing paragraph names the`cursor\` to pass for the next page.

When the project has no alerts yet, the output is a single line pointing at [`particle_alert_create`](/mcp/tools/alerts/alert-create).

Sample:

```markdown theme={"dark"}
## Alerts (2)

- OpenAI mentions — `dKxN6Ry2mL9pJ5qW` · ENTITY_MENTION · DAILY · 1 entity
  - **Status:** active
- Competitor watch — `7mPq3Wx9aL2nR5tV` · ENTITY_MENTION · WEEKLY · 4 entities
  - **Status:** paused
```

Passing `output_format: "json"` returns `alerts`, `has_more`, and `cursor` as compact JSON.

## Example

```text theme={"dark"}
Agent calls: particle_alert_list {}
            → reads an alert's `id` → "dKxN6Ry2mL9pJ5qW"

Agent calls: particle_alert_list_matches { "alert_id": "dKxN6Ry2mL9pJ5qW" }
```

## Related

* REST equivalent: [`GET /v1/projects/{projectId}/alerts`](/api-reference/alerts/list-alerts).
* Fetch one alert's full configuration with [`particle_alert_get`](/mcp/tools/alerts/alert-get).
* See what an alert has caught with [`particle_alert_list_matches`](/mcp/tools/alerts/alert-list-matches).
* Create a new alert with [`particle_alert_create`](/mcp/tools/alerts/alert-create).