Explain a failed n8n execution
execution_explainDiagnose a failed or surprising n8n execution. Paste the execution JSON (from the n8n UI 'Show details' or GET /executions/:id?includeData=true); returns a per-node summary highlighting nodes that returned 0 items, unresolved ={{ ... }} expressions, errors with hints, and LLM token usage. Hits the most common debugging pain point: items 'silently disappearing' between nodes. Deterministic, rule-based.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"execution": "<execution>"
},
"name": "execution_explain"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| execution | Yes | n8n execution payload (REST `?includeData=true` shape or raw UI export). Object or JSON string. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| findings | Yes | Per-node findings extracted from the execution payload. | |
| error_count | Yes | Number of error-severity findings. | |
| warning_count | Yes | Number of warning-severity findings. |