Get Run Error Clusters
get_run_error_clustersGroup a test run's failed and flaky tests by shared error signature to identify distinct failures, pinpoint the error affecting the most tests, and review category rollups.
Instructions
Group ONE run's failing tests by shared error signature (normalized error fingerprint), computed for that run only. Returns error clusters (each = one signature + its affected tests + an error category), an unclustered bucket for blank/unfingerprintable errors, a per-category rollup, and run totals. Failed/timed-out tests cluster on their final-attempt error; flaky tests cluster on the error they recovered from (pre-recovery). Categories: assertion, timeout, element_not_found, network, filesystem, setup (an e2e run that could not get started: credentials, environment, seed data, test setup, no model), other. Use this to answer "what are the distinct failures in this run?" or "which error affected the most tests?" — it is far cheaper than paging every failed case. Optionally narrow with status="failed" or status="flaky" (default "all"). Workflow: list_testruns() → pick a testrun_id → get_run_error_clusters().
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>",
"testrun_id": "<testrun_id>"
},
"name": "get_run_error_clusters"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| status | No | Which contributing tests populate the clusters (default "all") | |
| projectId | Yes | Project ID (e.g. project_<id>) | |
| testrun_id | Yes | The test run ID to cluster errors for (single run) |