Problem
The MCP Tool Call Segment event has a failure_detail field for the actual error message, but only the call-actor tool and the central tool-call catch in src/mcp/server.ts populate it. Other tool failure paths (get-actor-run, fetch-apify-docs) send the event with failure_detail empty — so in Segment we can see that those tools failed, but not why.
Fix
Populate failure_detail (and failure_category where missing) on every tool error path so the Segment event carries the error message consistently across all tools, matching what call-actor already does.
Problem
The
MCP Tool CallSegment event has afailure_detailfield for the actual error message, but only thecall-actortool and the central tool-call catch insrc/mcp/server.tspopulate it. Other tool failure paths (get-actor-run,fetch-apify-docs) send the event withfailure_detailempty — so in Segment we can see that those tools failed, but not why.Fix
Populate
failure_detail(andfailure_categorywhere missing) on every tool error path so the Segment event carries the error message consistently across all tools, matching whatcall-actoralready does.