Skip to main content
Glama
Milo0821

Zephyr Scale MCP Server

by Milo0821

search_test_runs

Find test runs in Zephyr Scale by project key, folder path, or folder ID. Filter results with optional fields and max results.

Instructions

Search for test runs using a query. Supports filtering by projectKey and/or folder path. On Cloud, only returns cycles in the exact folder (not sub-folders). Use folder_id for direct numeric ID lookup (skips path resolution).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoComma-separated list of fields to include in the response (optional, e.g., "key,name,status,folder"). If not set, all fields are returned.
folderNoFolder path to filter test runs by (e.g., "/MyFolder/SubFolder"). Resolved to a numeric folderId on Cloud.
folder_idNoNumeric folder ID to filter test runs by (optional). If provided, takes precedence over folder path and skips path resolution. Use this when you already know the folder ID.
max_resultsNoMaximum number of results to return (optional, default 200)
project_keyNoProject key to filter by (e.g., "PROJ"). Can be a single key or omitted if using folder only.
Behavior4/5

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

Discloses Cloud-specific behavior (exact folder) and folder path resolution. No annotations exist, so description covers key behavioral traits. No contradiction with 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?

Three concise sentences: purpose, filters, behavioral detail. Front-loaded and no wasted words.

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?

Covers all parameters and key behaviors. Lacks detail on the query string itself, but adequate given 5 parameters and no output schema.

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%, but description adds context beyond schema: folder precedence, default max_results, path resolution behavior. Improves agent understanding of parameter interactions.

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?

The description clearly states the tool searches for test runs using a query, specifies supported filters (projectKey, folder), and distinguishes behavior on Cloud (exact folder only). It differentiates from sibling tools like search_test_cases_by_folder.

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

Usage Guidelines4/5

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

Provides guidance on using folder_id to skip path resolution and notes Cloud limitation (no sub-folders). Implicitly suggests when to use folder vs folder_id, but lacks explicit when-not-to-use or alternative sibling comparison.

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/Milo0821/Zephyr_mcp_server'

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