errors
Why is my app broken, exceptions, stack traces, failures, recent errors, crash reports, debugging. One trace_id returns the complete ordered parent/child operation waterfall plus its correlated logs, errors, deploy failures, and journey events. No project lookup is required for that one-id path. Without a trace id, project_id returns the last 24h of failures from that project's functions. Each row carries kind: "exception" means nobody chose the outcome (an uncaught throw, or a 5xx) and "refusal" means a handler answered 4xx on purpose — a 401 from your own auth gate is a refusal, not a bug, and kind separates the two.
Example:
{ "project_id": "my-saas", "limit": 20 }
// Returns: [{ "timestamp": "2026-04-20T...", "path": "/api/users/signup", "status": 500, "message": "UNIQUE constraint failed: users.email" }, ...]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": "errors"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max number of errors to return (default: 10, max: 100) | |
| trace_id | No | Optional 32-character trace id returned by the platform. When supplied, returns the ordered waterfall and all correlated evidence; project_id is optional. | |
| project_id | No | Project ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them). |