Testsy

List runs

list_runs

Read-only

Recent runs, newest first, optionally for one test or project or with one status; or the runs with the given ids.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_runs"
  }
}

Input Schema

Name	Required	Description
`ids`	No	Comma-separated run ids (j_…, up to 50): returns their full views
`limit`	No	At most this many (default 50, up to 200)
`status`	No	Only this status
`testId`	No	Only this test
`projectId`	No	Only this project

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.5/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish that this is a read-only, non-open-world operation. The description adds useful behavior such as newest-first ordering and that id lookups return full views, but it does not discuss pagination behavior or what non-id results contain.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single compact sentence with the main behavior front-loaded. Every clause contributes to describing ordering, filtering, or id lookup, with no unnecessary wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter list tool with no output schema, the description covers the main lookup modes and ordering. It leaves some ambiguity around 'recent', pagination, and what the default run summaries contain versus the full views returned by ids.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the parameters are already well documented. The description adds some meaning by presenting filters and id lookup as alternative modes, but it largely restates what the schema already conveys.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that this tool lists runs, with ordering and optional filtering by test, project, status, or explicit ids. It is specific enough to distinguish the core listing behavior, though it does not explicitly name sibling tools such as get_run as alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It indicates the available usage modes: recent runs with optional filters, or runs by ids. However, it does not explain when to prefer this over get_run or how to choose among overlapping filters beyond a brief 'or' construction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Testsy tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.