Skip to main content
Glama
testdino-hq

TestDino MCP

by testdino-hq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Manual Test Runs

list_manual_runs
Read-only

Browse and filter manual test runs by status, state, environment, release, tags, or name to find specific runs in a project.

Instructions

Browse manual test runs for a project. Filter by status (active|closed), state (new|in_progress|on_hold|done), environment, release (releaseId), tags, or free-text search on name. Default page size 25 (max 200).

Input Schema

NameRequiredDescriptionDefault
pageNo
tagsNoSingle tag or comma-separated tags
limitNoDefault 25
stateNoWorkflow state. Either canonical ("new", "in_progress", "on_hold", "done") or display ("In Progress", "On Hold") form — server normalizes to lowercase+underscored so UI colors render correctly.
searchNoMatch by run name
sortByNo
statusNo
isClosedNo
projectIdYesProject ID
releaseIdNoFilter to runs in this release. Pass "none" to list unlinked runs.
sortOrderNo
environmentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv2.2.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / limit / description
      Previous value: -"Default 25 (max 200)."New value: +"Default 25"
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / page / minimum
      Added value: +1
    • changedInput schema / properties / page / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / projectId / description
      Previous value: -"Project ID (required)."New value: +"Project ID"
    • changedInput schema / properties / releaseId / description
      Previous value: -"Filter to runs in this release. 'none' = unlinked."New value: +"Filter to runs in this release. Pass \"none\" to list unlinked runs."
    • changedInput schema / properties / search / description
      Previous value: -"Match by run name."New value: +"Match by run name"
    • changedInput schema / properties / state / description
      Previous value: -"Workflow state. Either canonical ('in_progress', 'on_hold', 'done') or display ('In Progress', 'On Hold') form — the server normalizes lowercase+underscored."New value: +"Workflow state. Either canonical (\"new\", \"in_progress\", \"on_hold\", \"done\") or display (\"In Progress\", \"On Hold\") form — server normalizes to lowercase+underscored so UI colors render correctly."
    • changedInput schema / properties / tags / description
      Previous value: -"Single tag or comma-separated."New value: +"Single tag or comma-separated tags"
  2. Addedv1.0.10

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already covers the safety profile. The description adds pagination defaults (page size 25, max 200), which is useful behavioral context the annotation doesn't provide, but omits sort behavior and return characteristics.

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?

Two sentences, filter options grouped efficiently, and the pagination default is placed at the end. No wasted words.

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 12-parameter list tool with no output schema, the description covers the filter surface but leaves entire parameters (sortBy, sortOrder, isClosed) unexplained and provides no return-format guidance. Adequate but with clear gaps.

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 only 50%, and the description restates the status/state/environment/release/tags/search filters already documented in the schema, though it helpfully lists the allowed status and state values. It does not compensate for the undocumented parameters like sortBy, sortOrder, isClosed, or page.

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 clear verb+resource ('Browse manual test runs for a project') and enumerates the filterable dimensions. It doesn't explicitly differentiate from near-siblings like list_testruns or get_manual_run, so it stops short of a 5.

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 implies a browsing/listing use case by describing filters, but never states when to use this tool vs list_testruns or get_manual_run for a single run. No when-not guidance is provided.

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

Deploy Server

Other Tools