get_execution_detail
Get detailed results of a test execution (campaign or Tests-campaign runs).
Get detailed results of a test execution (campaign or Tests-campaign runs).
Read-only · Calls external systems. Safe to call: this tool does not modify data.
Parameters
| Field | Type | Required | Description |
|---|---|---|---|
include_full_json | boolean | No | Set to true to include the raw json field containing the complete execution payload with full action step details. Warning: this can be very large for multi-test campaigns. Only use when you need step-level detail beyond what execution_summary provides. |
result_id | string | Yes | The execution/result ID. Obtain from run_campaign response, poll_execution response, start_execution response, or list_executions results. |
Example arguments
Illustrative arguments an agent supplies when calling this tool:
{
"result_id": "string"
}Description
Returns metadata plus a per-test view: execution_summary (per-test/per-action status, duration, variables, error messages) when the execution's JSON is available, or a lightweight tests_overview for queued/running results without it. Failed tests are always included; surplus passing tests may be elided in very large campaigns (see tests_elided / tests_overview_omitted). Set include_full_json=true when you need step-level details (selectors, HTTP payloads) or the complete per-test list. For monitoring (scheduled) runs use get_monitoring_result instead.Related
What's next?
Last updated on