tuskr-mcp-server

List Test Runs

list_test_runs

Retrieve test runs for a specified project using filters for key, name, status, assignee, and completion to locate active, archived, or incomplete runs.

Instructions

Retrieves list of test runs of a project with support for various filters.

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": {
      "filter_project": "<filter_project>"
    },
    "name": "list_test_runs"
  }
}

Input Schema

Name	Required	Description
`page`	No	controls number of records in output, every page contains 100 records. Default is 1. Ignored when filter_incomplete is True.
`filter_key`	No	to filter test runs with key containing the specified value
`filter_name`	No	to filter test runs with name containing the specified value
`filter_status`	No	to filter test runs by their status. Two supported values 'active' or 'archived'
`filter_project`	Yes	specifies the project ID to filter the test runs associated with a particular project
`filter_incomplete`	No	if True, fetches all pages and returns only test runs that are not 100% complete, with a trimmed payload (id, key, name, percentDone, counts, assignee, deadline, status). When False (default), returns the paginated response from the Tuskr API with every field intact. Either way the assignee on each row is reduced to id, fullName and email.
`filter_assigned_to`	No	id of the user to whom test runs are assigned

Schema Changelog

Changes observed during successful MCP inspections.

Changed24 schema fields changedv0.1.5Oct 25, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / filter_assigned_to / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / filter_assigned_to / description
```
Added value: +"id of the user to whom test runs are assigned"
```
removedInput schema / properties / filter_assigned_to / title
```
Removed value: -"Filter Assigned To"
```
removedInput schema / properties / filter_assigned_to / type
```
Removed value: -"string"
```

addedInput schema / properties / filter_incomplete / description

Added value: +"if True, fetches all pages and returns only test runs that are not 100% complete,\nwith a trimmed payload (id, key, name, percentDone, counts, assignee, deadline, status).\nWhen False (default), returns the paginated response from the Tuskr API with every field\nintact. Either way the assignee on each row is reduced to id, fullName and email."

removedInput schema / properties / filter_incomplete / title
```
Removed value: -"Filter Incomplete"
```

addedInput schema / properties / filter_key / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / filter_key / description

Added value: +"to filter test runs with key containing the specified value"

removedInput schema / properties / filter_key / title
```
Removed value: -"Filter Key"
```
removedInput schema / properties / filter_key / type
```
Removed value: -"string"
```

addedInput schema / properties / filter_name / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / filter_name / description

Added value: +"to filter test runs with name containing the specified value"

removedInput schema / properties / filter_name / title
```
Removed value: -"Filter Name"
```
removedInput schema / properties / filter_name / type
```
Removed value: -"string"
```

addedInput schema / properties / filter_project / description

Added value: +"specifies the project ID to filter the test runs associated with a particular project"

removedInput schema / properties / filter_project / title
```
Removed value: -"Filter Project"
```
addedInput schema / properties / filter_project / type
```
Added value: +"string"
```

addedInput schema / properties / filter_status / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / filter_status / description

Added value: +"to filter test runs by their status. Two supported values 'active' or 'archived'"

removedInput schema / properties / filter_status / title
```
Removed value: -"Filter Status"
```
removedInput schema / properties / filter_status / type
```
Removed value: -"string"
```

addedInput schema / properties / page / description

Added value: +"controls number of records in output, every page contains 100 records. Default is 1.\nIgnored when filter_incomplete is True."

removedInput schema / properties / page / title
```
Removed value: -"Page"
```

First observedv0.1.2Jul 29, 2026

TDQS

C2.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about pagination (100 records/page), the special all-pages/trimmed-payload mode of filter_incomplete, or the reduced assignee shape. All of that critical behavior lives only in the schema and is invisible at description level.

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

Conciseness3/5

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

One short sentence, front-loaded and waste-free, but its brevity comes from under-specification rather than economy. It says nothing that the name and schema do not already convey.

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

Completeness2/5

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

For a 7-parameter read tool with no annotations and no output schema, the description omits required-parameter context (filter_project), pagination semantics, and the materially different response shape triggered by filter_incomplete. An agent could call it, but would not understand what it gets back.

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 schema already documents all 7 parameters well. The description adds nothing beyond 'various filters', landing at the baseline for fully-documented schemas.

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

Purpose3/5

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

States a specific verb and resource ('Retrieves list of test runs of a project'), which is clearer than a tautology. However, it does not distinguish this from close siblings like get_test_run_details, bulk_export_test_runs, or archive_test_runs; 'with support for various filters' is too generic to route an agent.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no alternatives named. The agent has to infer from sibling names whether listing, exporting, or fetching details is appropriate.

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

Deploy Server