List test runs

testrun.listReadsOnly looks things up; never changes your workspace.

What it does

Lists the test runs in the connected workspace, newest first, 20 per page, optionally filtered by name. A test run is one execution of a set of test cases, with a Pass / Fail / Not Executed result per case. Use it to find a recent run to grade with pdlc.verify, or to decide whether a fresh run is needed. Returns { items: [{ id, uri, name, status, verdict, gitSha, branch, workingTreeClean, releaseId, pdlcSessionId, startDate, endDate }], page, totalPages, totalItems }. status is the run's lifecycle (e.g. ACTIVE), not its outcome. verdict is a count summary { passed, failed, blocked, skipped, pending, total, passRate } (passRate is 0-100, or null when nothing was executed), not a ship decision; call pdlc.verify for the deterministic pass/fail verdict. Read-only.

Ask your agent

You don’t call testrun.list yourself. Say something like this to Claude Code, Cursor or another MCP-connected agent:

  • “Did the last test run pass?”
  • “Show me the recent test runs”
  • “Find the run we did for the checkout release”

Inputs

NameTypeDescription
title
optional
stringCase-insensitive text to look for in the run name, e.g. "checkout". Omit to list all runs.
page
optional
integerPage number, starting at 1 (default 1). Each page holds up to 20 runs, newest first; check totalPages.

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.list",
    "arguments": {
      "title": "<title>"
    }
  }
}

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.