Skip to main content
Glama

List Launch Test Results

list_launch_test_results
Read-onlyIdempotent

Retrieve test results from a specific launch, including manual execution metadata. Filter by failed or manual results, apply search criteria, paginate, and sort to pinpoint the outcomes you need.

Instructions

List test results inside a launch, including manual execution metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoZero-based page index after optional filtering.
sizeNoNumber of results per page (max 100).
sortNoOptional sort directives such as ['name,ASC'] or ['createdDate,DESC'].
searchNoOptional result-name search term.
filter_idNoOptional saved filter ID from TestOps.
launch_idYesLaunch ID (required).
project_idNoOptional override for the default Project ID.
failed_onlyNoWhen true, return only failed or broken results. Filtering is handled for you.
manual_onlyNoWhen true, return only manual results. Filtering is handled for you.
output_formatNoOutput format: 'json' (default) or 'plain'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
sizeNo
itemsNoEntity-specific collection entries.
totalNo
launch_idNo
failed_onlyNo
manual_onlyNo
total_pagesNo
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds a minor behavioral detail ('including manual execution metadata') beyond annotations. However, it does not disclose pagination, filtering behavior, or error conditions, which are not covered by annotations.

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?

The description is a single concise sentence that front-loads the key action. Every word is necessary, with no wasted text.

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

Completeness2/5

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

Despite the presence of an output schema and comprehensive parameter descriptions, the tool has 10 parameters and the description is very brief. It lacks context on what test results are, how manual execution metadata relates, or how the various filtering and pagination parameters should be used.

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 description coverage is 100%, so the schema already documents all parameters thoroughly. The tool description adds no additional meaning to the parameters; it does not mention any parameter or usage hints.

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 clearly states the tool lists test results inside a launch, including manual execution metadata. It uses a specific verb and resource, and while it doesn't explicitly contrast with sibling tools, the focus on 'test results' distinguishes it from tools like 'list_test_cases' or 'get_launch'.

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

Usage Guidelines2/5

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

The description provides no when-to-use or when-not-to-use guidance. It does not mention alternatives or context for choosing this tool over similar list tools such as 'list_test_cases' or 'list_defects'.

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/ivanostanin/lucius-mcp'

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