Get one test run
testrun.getReadsOnly looks things up; never changes your workspace.What it does
Reads the summary of one test run in the connected workspace: { id, uri, name, buildVersion, description, startDate, endDate, status, gitSha, branch, workingTreeClean, releaseId, frozen, numberOfTestCases }. A run from another workspace is reported as not in the active space. It does not include per-case results or a pass/fail decision; for those call pdlc.verify with the same testRunId (read-only, deterministic). Get the id from testrun.list or from the testrun.create result. Read-only.
Ask your agent
You don’t call testrun.get yourself. Say something like this to Claude Code, Cursor or another MCP-connected agent:
- “How many tests were in yesterday's run?”
- “Show me the details of the release 2.0 test run”
- “What build did the last run test?”
Inputs
| Name | Type | Description |
|---|---|---|
testRunIdrequired | string | Test run id: the id from testrun.list or testrun.create (e.g. "AAtr-kzqd-mwpe-rtya-hbnc-xufo-lgsi"). |
The MCP call
What the agent’s MCP client sends (placeholders in angle brackets):
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "testrun.get",
"arguments": {
"testRunId": "<testRunId>"
}
}
}Connect your agent
npx -y @testmaze/mcp init tmt_xxx claude mcp add tm --scope project -- npx -y @testmaze/mcp
Create the token in your Test Maze workspace under Settings → MCP. Setup for Cursor, Cline, Gemini CLI and Codex CLI is shown there too.
More test runs tools
- List test runs
testrun.list - Record test results on a run
testrun.record_results - Create a test run
testrun.create