Testiny Test Management

List Testiny test runs

listTestRuns

Read-onlyIdempotent

Retrieve a list of Testiny test runs with an optional keyword filter

Input Schema

Name	Required	Description
`format`	No	Format for rich-text fields (descriptions, preconditions, comments, step & result cells, stepsText & expectedResultText) on both input and output: 'markdown' (default) or 'xml'. Read the matching rich-text format reference resource before producing either. Use 'xml' for BOTH the read and the write whenever you are changing a field that already has content: markdown cannot carry an underline or a text color, so an edit written as markdown writes those away. 'markdown' is for writing new content and for reading you will not edit.
`keyword`	No	An optional keyword to search in test run titles. A keyword of digits only, optionally prefixed 'TR-' or '#', looks up that id instead of searching titles.
`project`	Yes	Project ID (number or string), project key or part of the project name

Output Schema

Name	Required	Description	Default
`testRuns`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 12, 2026

addedInput schema / properties / format

Added value: +{
+  "description": "Format for rich-text fields (descriptions, preconditions, comments, step & result cells, stepsText & expectedResultText) on both input and output: 'markdown' (default) or 'xml'. Read the matching rich-text format reference resource before producing either. Use 'xml' for BOTH the read and the write whenever you are changing a field that already has content: markdown cannot carry an underline or a text color, so an edit written as markdown writes those away. 'markdown' is for writing new content and for reading you will not edit.",
+  "enum": [
+    "markdown",
+    "xml"
+  ],
+  "type": "string"
+}

changedInput schema / properties / keyword / description

Previous value: -"An optional keyword to search in test run titles. When looking for an id, search in the following format: TR-1234"New value: +"An optional keyword to search in test run titles. A keyword of digits only, optionally prefixed 'TR-' or '#', looks up that id instead of searching titles."

addedOutput schema / properties / testRuns / items / properties / _etag

Added value: +{
+  "description": "Conflict tag of the entity - pass it to an edit tool's '_etag' to have that edit rejected if somebody changed the entity in the meantime. Empty for an entity that carries no tag yet.",
+  "type": "string"
+}

changedOutput schema / properties / testRuns / items / required

Previous value: -[
-  "id",
-  "title",
-  "testplan",
-  "description",
-  "isClosed"
-]New value: +[
+  "id",
+  "title",
+  "testplan",
+  "description",
+  "isClosed",
+  "_etag"
+]

First observedOct 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds nothing beyond that — no statement of result scope, pagination behavior, or whether all runs in the project are returned. It largely restates what the structured fields already convey.

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?

A single well-formed sentence with the core action front-loaded and no filler. Nothing in it is redundant or wasted.

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?

The output schema exists, so return values need not be explained, and the input schema covers all three parameters fully. However, for a list tool with no pagination or limit parameters, the description should say whether the result set is bounded or complete for the project — that scope question is left unanswered.

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 'format', 'keyword', and 'project' including the id-lookup semantics and the markdown/xml trade-off. The description only repeats the keyword filter idea ('optional keyword filter') without adding format or project detail, so baseline 3 is correct.

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?

States a specific verb and resource ('Retrieve a list of Testiny test runs') plus the scoping option ('optional keyword filter'). It is clearly distinguishable from write siblings like createTestRun and setTestResult, but it never names a list sibling (e.g. listTestCases) or clarifies why one would pick this over them.

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?

The only usage cue is that the filter is optional; there is no statement of when to use this versus listTestCases/listProjects, no prerequisite context, and no exclusion. The agent must infer the use case entirely.

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

All Testiny Test Management tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?