Skip to main content
Glama

List Test Cases In A Run

list_run_test_cases
Read-only

List per-case execution records in a manual test run, including caseKey, title, assignee, and status; filter by assignee or result and retrieve rtcRef before updating a case.

Instructions

Get the per-case execution records inside a manual run — what the UI shows as rows in the run's test-case table. Each row carries the test case identity (caseKey like "TC-156", title), the current assignee, and the current result/status ("untested", "passed", "failed", etc.). Filter by assignee (email or User _id) or result/status. Use this before update_run_test_case so you have the rtcRef for each case you want to update.

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>",
      "runId": "<runId>"
    },
    "name": "list_run_test_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNoDefault 25
runIdYesInternal run _id or counter-style ID e.g. "RUN-12"
resultNoFilter by result/status. Display ("Passed") or canonical ("passed") form.
searchNoMatch by case title or caseKey
sortByNo
statusNoAlias for `result`. Same normalization rules.
assigneeNoFilter by assignee — User _id OR email (server resolves).
projectIdYesProject ID
sortOrderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 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 / assignee / description
      Previous value: -"Filter by assignee — User _id OR email (server resolves email)."New value: +"Filter by assignee — User _id OR email (server resolves)."
    • 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 / result / description
      Previous value: -"Filter by result/status. Display ('Passed') or canonical ('passed') form."New value: +"Filter by result/status. Display (\"Passed\") or canonical (\"passed\") form."
    • changedInput schema / properties / runId / description
      Previous value: -"Internal run _id or counter-style ID e.g. 'RUN-12' (required)."New value: +"Internal run _id or counter-style ID e.g. \"RUN-12\""
    • changedInput schema / properties / search / description
      Previous value: -"Match by case title or caseKey."New value: +"Match by case title or caseKey"
    • changedInput schema / properties / status / description
      Previous value: -"Alias for result."New value: +"Alias for `result`. Same normalization rules."
  2. Addedv1.0.10

TDQS

A4.3/5.0
Behavior4/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 safety is covered. The description adds context beyond that: the row contents returned, the display-vs-canonical status normalization, and the rtcRef contract that the downstream update tool needs. It omits pagination behavior and default page size, which is a minor gap given annotations carry the safety profile.

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?

Front-loaded with the definition, then row contents, then filtering, then the workflow hint — a sensible order with no filler sentences. The filtering sentence partially duplicates schema descriptions, which keeps it from a 5 but does not make it bloated.

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?

A 10-parameter tool with no output schema needs the description to describe returns, and it does: test case identity, assignee, and result/status per row. What remains unstated is pagination/default page size and sort behavior, though those are covered by schema descriptions.

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 70%, so baseline is 3. The description restates the assignee semantics (email or User _id) and the result/status values, but those are already in the schema; it adds no guidance for page, limit, search, sortBy, or sortOrder. Marginal value beyond structured fields.

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?

States a specific verb and resource: per-case execution records inside a manual run, and anchors it to the UI's run test-case table. It also names what each row carries (caseKey, title, assignee, result/status), which separates it from list_manual_test_cases (definitions) without needing to see the sibling.

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

Usage Guidelines5/5

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

"Use this before update_run_test_case so you have the rtcRef for each case you want to update" gives explicit sequencing and names the dependent sibling. It also states the two filtering axes (assignee, result/status), so an agent knows how to narrow instead of paging through everything.

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