Get API Test Runs
get_api_test_runsPage through an API test's recent run history — each run's outcome (SUCCESS, FAILURE, ERROR, MISSED, RATE_LIMITED), its latency (ttfbMillis, totalMillis) and 'timing', which splits the run into its steps (one 'request' step for an HTTP test; for an MCP test, every step of the conversation its protocol and assertion tier define, in order, whether or not the run reached it: initialize, notifications/initialized, tools/list, tools/call (stream first on the 2024-11-05 transport; server/discover instead of the handshake on 2026-07-28)) and each step into dnsMillis, connectMillis, tlsMillis, serverMillis and downloadMillis. A phase the step did not perform is null, a step the run never reached has every phase null, and the first such step is where the run stopped; DNS, connect and TLS on a step mean a new connection was opened for that step (on the 2024-11-05 transport the stream keeps its own connection, so initialize always opens one), and 'remoteAddress' and 'connectionReused' say which address answered and whether the connection was already open. Runs from before this field have 'timing' null. A run also carries any assertion failures and its traceId: the W3C trace id the probe sent to the target as a traceparent header, so the target's own logs and traces for that run can be found by trace_id. A RATE_LIMITED run means the target answered HTTP 429 to the monitor: the run was not retried, the next run was deferred by the target's Retry-After (retryAfterSeconds), and it does not count toward uptime. For MCP tests, 'protocolRevision' is the protocol revision that run spoke, and 'previousRevision' is set when a NEWEST_SUPPORTED test moved to a newer revision in that run. Use this to investigate why an API test is unhealthy. Optionally filter by time window and status. The redacted request/response capture of each run is available on the HTTP API only.
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": {
"apiTestId": "<apiTestId>"
},
"name": "get_api_test_runs"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | End of the window, ISO-8601 instant (inclusive) | |
| from | No | Start of the window, ISO-8601 instant e.g. '2026-07-01T00:00:00Z' (inclusive) | |
| page | No | Zero-based page number (default 0) | |
| size | No | Runs per page — default and max 200; values outside 1-200 are clamped | |
| status | No | Filter to one outcome: SUCCESS, FAILURE, ERROR, MISSED or RATE_LIMITED | |
| apiTestId | Yes | Id of the API test whose runs to fetch |