Skip to main content
Glama
vilaabo

zephyr-scale-mcp

by vilaabo

create_test_run

Create a Zephyr Scale test run (test cycle) with a fixed set of test cases and optional execution results. The run composition is immutable after creation, so provide all items at once.

Instructions

Create a Zephyr Scale test run (test cycle; key like PROJ-R123). IMPORTANT API v1 limitation: a test run is IMMUTABLE after creation — there is no PUT /testrun/{key}. A run cannot be renamed, moved to another folder, and test cases cannot be added to or removed from it later; the set of items is fixed ONLY at creation time. The run status is computed automatically from the statuses of its items and cannot be set directly. Therefore pass the COMPLETE list of test cases in items now — each item may also carry full execution result fields (status, executedBy, executionTime, actualStartDate/actualEndDate, per-step scriptResults, etc.), which allows importing a run together with its results in a single call. To record or update executions of the included items afterwards, use the test result tools. Item/result statuses default to 'Not Executed', 'In Progress', 'Pass', 'Fail', 'Blocked' (case-sensitive; instances may define custom ones).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesTest run name (cannot be changed after creation)
itemsNoTest cases to include in the run — this is the ONLY place where the run composition can be set. Each item requires testCaseKey and may carry full execution result fields (status, environment, executedBy, assignedTo, comment, executionTime, actualStartDate, actualEndDate, customFields, issueLinks, scriptResults).
ownerNoOwner. Jira *user key* (e.g. 'JIRAUSER10000'), NOT a username or e-mail — resolve it with find_jira_user.
folderNoFull path of a TEST_RUN folder starting with "/", e.g. "/Regression". The folder MUST already exist (create it with create_folder, type TEST_RUN); it is not created automatically.
versionNo
iterationNo
issueLinksNoJira issue keys to link, e.g. ["PROJ-123"]
projectKeyNoJira project key; defaults to ZEPHYR_DEFAULT_PROJECT_KEY
testPlanKeyNoKey of the test plan to associate the run with, e.g. PROJ-P123
customFieldsNoCustom field values keyed by field name
plannedEndDateNoISO 8601 (passed through as-is)
plannedStartDateNoISO 8601, e.g. 2026-07-20T00:00:00Z (passed through as-is)
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: immutability, automatic status computation, case-sensitive status values, and the inability to rename or move. It also explains the default statuses.

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?

The description is structured with a clear 'IMPORTANT' section and front-loads critical limitations. However, it is somewhat verbose; a slightly more concise version would improve readability without losing value.

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?

Given the tool's complexity (12 parameters, nested objects, no output schema), the description is comprehensive. It covers creation constraints, parameter details, defaults, and references sibling tools, leaving minimal gaps for an AI agent.

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 high (83%), but the description adds meaningful context beyond the schema, such as the requirement for Jira user keys, folder existence precondition, and case sensitivity of statuses. This adds value while the schema already documents most parameters.

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 creates a Zephyr Scale test run, specifying the key format (PROJ-R123). It distinguishes from siblings by explaining that after creation, updates to executions should use test result tools.

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?

The description explicitly warns about the API v1 limitation: the test run is immutable after creation. It advises passing the complete list of items now and points to test result tools for later updates, providing clear when-to-use and when-not-to-use guidance.

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/vilaabo/zephyr-scale-mcp'

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