List error issues
list_error_issuesStart here to see what is broken: grouped issues from the backend and the app together, each with its source, level, status, event and user counts. Newest activity first, unresolved only. Console lines from the app are hidden unless include_console is true. Pass next_cursor to read on.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "list_error_issues"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Default last_seen. new = first seen most recently | |
| level | No | ||
| limit | No | Rows (default 25) | |
| since | No | Last seen since: an ISO time, or 30m, 24h, 7d | |
| cursor | No | next_cursor from the last answer | |
| source | No | The server, the app, or both (default all) | |
| status | No | Which issues (default unresolved) | |
| release | No | Text in a release the issue was seen in: 2.0.77+185, or package@2.0.77+185 | |
| platform | No | Like python, ios, android | |
| environment | No | Issues with an event in this environment | |
| include_spark | No | Add a 14-day sparkline per row (default false) | |
| include_legacy | No | Also list issues grouped before grouping v2 (default false) | |
| include_console | No | Also list console lines from the app (default false) |