Skip to main content
Glama

list_testruns

Browse and filter test runs by branch, status, time, environment, author, or tags to locate specific executions. Sort and paginate results for efficient review.

Instructions

Browse and filter your test runs to find specific test executions. Filter by git branch (e.g., 'develop', 'main'), run status ('passed', 'failed', 'interrupted', 'incomplete', 'running'), time interval ('Latest', '1h', '2h', '5h', '1d', '3d', '5d', 'weekly', 'monthly', or custom date ranges), commit author, environment (e.g., 'production', 'staging', 'development'), or test case tags. Search commit messages (or an exact run counter when numeric) with 'search', and order results with 'sort'. Supports efficient pagination using page/limit or offset/limit. Returns test run summaries with statistics (total, passed, failed, skipped, flaky counts), duration, status, branch, author, and PR information when available. Perfect for answering questions like 'What tests ran on the develop branch?' or 'Show me all failed runs from last hour.' The PAT should be configured in mcp.json as TESTDINO_PAT environment variable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default: 1).
sortNoSort order for the run list: 'counter_desc' (newest first, default), 'counter_asc', 'duration_asc', or 'duration_desc'.
limitNoNumber of results per page (default: 20, max: 1000).
searchNoSearch run commit messages, or match an exact run counter when the value is numeric.
by_authorNoFilter by commit author name (exact match).
by_branchNoFilter by git branch name (e.g., 'main', 'develop', 'feature/login').
by_commitNoFilter by git commit hash (full or partial).
by_statusNoFilter by run status: 'passed', 'failed', 'interrupted', 'incomplete', or 'running'.
projectIdYesProject ID (Required). The TestDino project identifier.
by_environmentNoFilter by environment. Example: 'production', 'staging', 'development'.
by_time_intervalNoFilter by time interval. Supports: 'Latest' (most recent, no time filter), '1h' (last hour), '2h' (last 2 hours), '5h' (last 5 hours), '12h' (last 12 hours), '1d' (last day), '3d' (last 3 days), '5d' (last 5 days), 'weekly' (last 7 days), 'monthly' (last 30 days), 'last 1 hour', 'last day', 'last 5 days', or '2024-01-01,2024-01-31' (date range).
by_test_case_tagsNoComma-separated test case tags contained in the run (exact match, include the '@' prefix if the tag has one, e.g. '@critical').
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses read-only browse semantics, search behavior (commit messages or exact run counter), pagination support, return fields (statistics, duration, etc.), and the TESTDINO_PAT setup requirement. It stops short of explicitly stating 'does not modify anything', but 'browse and filter' implies a non-mutating operation.

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

Conciseness4/5

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

The description is longer than minimal but well-structured: purpose, filters, pagination, return values, examples, auth note. Some filter details are redundant with the schema, but the examples and return-value description justify the length. It is front-loaded and organized.

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

Completeness4/5

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

For a 12-parameter tool with no output schema, the description covers filter semantics, return summaries, pagination, and authentication. It misses an explicit note on default time interval or handling no results, and the offset/limit mention conflicts with the schema. Overall, it is quite complete for the complexity.

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 coverage is 100%, so the baseline is 3. The description adds helpful examples (branch names, environment values, time intervals, tag '@' prefix) but also introduces a potential inconsistency by mentioning 'offset/limit' pagination even though 'offset' is not a schema parameter. This ambiguity prevents a higher score.

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

Purpose5/5

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

The description uses a specific verb+resource ('Browse and filter your test runs') and clearly states the tool's scope: finding specific test executions. It differentiates from siblings like get_run_details and list_run_test_cases by focusing on run-level filtering rather than details or test-case listing.

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

Usage Guidelines4/5

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

The description provides clear usage context with concrete examples ('Perfect for answering questions like...') and enumerates the filter dimensions. It does not explicitly name alternative tools or state when not to use this tool, so it misses the top score.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/testdino-hq/testdino-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server