Skip to main content
Glama

Get Manual Test Run

get_manual_run
Read-only

Retrieve full details for a single manual test run by project and run ID, including status, environment, linked release, test statistics, contributors, attachments, and linked issues.

Instructions

Get the full details of one manual test run: name, status, environment, linked release, test stats (total/passed/failed/blocked/untested), contributors, attachments, linked issues. runId accepts either the internal _id or a counter-style ID like "RUN-12".

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": "get_manual_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesInternal _id or counter-style ID
projectIdYesProject ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 / projectId / description
      Previous value: -"Project ID (required)."New value: +"Project ID"
    • changedInput schema / properties / runId / description
      Previous value: -"Internal _id or counter-style ID (required)."New value: +"Internal _id or counter-style ID"
  2. Addedv1.0.10

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description contributes the returned field set and the accepted ID formats, but says nothing about behavior on an unknown runId, permission requirements, or cost/latency for a potentially heavy aggregate.

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, front-loaded with the resource and return contents, with the ID-format caveat placed after the main purpose. Every clause carries information; nothing is redundant with the name or title.

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

Completeness5/5

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

With no output schema, listing the returned fields is exactly the right compensation, and both required parameters plus their ID formats are covered. For a two-parameter read-only fetch backed by full annotations, no material gap remains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already distinguishes internal _id from counter-style ID, so baseline would be 3. The description adds a concrete example format ('RUN-12'), which is meaningfully more actionable than the schema text alone.

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?

The description states a specific verb ('Get') and resource ('one manual test run') and enumerates the payload fields, so the agent knows exactly what comes back. It does not explicitly differentiate itself from similar siblings such as get_run_details or list_manual_runs, which keeps it below 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?

Usage is only implied: 'one manual test run' signals single-record retrieval versus listing, but there is no explicit when-to-use statement, no mention of when a different retrieval tool is appropriate, and no prerequisites. Adequate but not instructive.

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