Get Test Run Details
get_run_detailsRetrieve complete summary details for one or more test runs, including result counts, timing, git/CI metadata, Playwright settings, shards, re-runs, and quarantine status.
Instructions
Get the summary of one or more test runs: result counts, timing, git branch and commit, CI pipeline, Playwright settings, shards, re-runs and quarantine. It does not list the run's tests: use list_testcase with by_testrun_id for those. Use testrun_id for ID-based lookup or counter for the human-readable run number (e.g. counter="47"). Batch up to 20 runs by comma-separating: testrun_id="id1,id2,id3". Typical workflow: list_testruns() → pick IDs → get_run_details() for the specific run. When is_swarm is true the run was distributed across multiple CI machines and the response also carries machines[] (per-machine counts plus spec_files, duration_ms and idle_tail_ms), machine_summary (machine_count, slowest, fastest, imbalance_ratio) and could_not_execute_specs — specs no machine could run, which means the run is not a clean pass whatever the counts say. Use the optimize_swarm prompt to turn those into a verdict; a file never splits across machines, so a slowest machine running one spec file is a hard floor that more machines cannot beat. Set include_ai_insights=true (single testrun_id only) to also get the run's AI Insights under ai_insights: AI failure categorization (flaky/bug/ui_change), failure clusters, new-failures cards, the error-analysis table, and the LLM-written run summary. AI payloads are generated lazily — if ai_insights sections report status "processing"/"not_generated", poll get_ai_insights(testrun_id=...) until "completed" instead of re-calling this tool. An "unavailable" section carries the upstream statusCode: a 5xx or timeout is transient (retry once via get_ai_insights), a 4xx (bad ids) is terminal.
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": {
"projectId": "<projectId>"
},
"name": "get_run_details"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| counter | No | Run counter. Number for a single run (e.g. 47), or comma-separated string ("47,48,49", max 20) for batch lookup. | |
| projectId | Yes | Project ID | |
| testrun_id | No | Single test run ID, or comma-separated IDs (max 20) | |
| include_ai_insights | No | Attach the run's AI Insights (categorization, clusters, error-analysis table, written summary) under `ai_insights`. Requires a single testrun_id (not counter, not a batch). |