Skip to main content
Glama

List Manual Test Runs

list_manual_runs
Read-only

Browse and filter manual test runs for a project by status, state, environment, release, tags, or run name to quickly locate the runs you need.

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).

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": {
      "projectId": "<projectId>"
    },
    "name": "list_manual_runs"
  }
}

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds pagination behavior ("Default page size 25 (max 200)"), though that partly restates the schema's limit description, and it says nothing about return shape, total counts, or empty results — for a list tool with no output schema this leaves a gap.

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?

Two dense sentences, front-loaded with purpose before filters and pagination limits. The parenthetical value enumerations duplicate the schema enums almost verbatim, which is minor waste but not obfuscating.

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 read tool with no output schema, the description covers the filtering dimension adequately but omits sorting defaults (sortBy/sortOrder), whether results are paginated with a cursor or offset, and how isClosed relates to status. An agent could call it, but would have to experiment to learn the response shape.

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?

With 50% schema coverage, the description compensates on the filter side by enumerating status values, state values, and mapping release to releaseId, plus clarifying that search matches on name. It leaves page, sortBy, sortOrder, isClosed and the relationship between isClosed and status unexplained, so half the parameter surface still relies on terse schema text.

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?

"Browse manual test runs for a project" gives a specific verb (browse/list), resource (manual test runs) and scope (project-scoped), which separates it from create_manual_run or list_run_test_cases. It never explicitly names a sibling to contrast with, so the differentiation is inferred from the resource noun rather than stated.

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?

The description explains how to narrow results (status, state, environment, release, tags, free-text search) but gives no guidance on when to choose this tool over get_manual_run or list_run_test_cases. Usage is implied by the tool name and filter list rather than stated.

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