Skip to main content
Glama
alejandroviera

zephyr-squad-server-mcp

add_tests_to_cycle_from_list

Add specified test issues as new UNEXECUTED executions directly into a test cycle. Supports both synchronous waiting and async token return.

Instructions

Add an explicit list of tests to a cycle as new UNEXECUTED executions.

issues is a list of Zephyr Test issue keys/ids (e.g. ["PROJ-1", "PROJ-2"]); a comma-separated string is also accepted and split automatically. project/version accept keys/names or ids (prefer ids to skip a lookup; -1 = Unscheduled). Async: with wait=True (default) polls to completion and returns the final job payload; with wait=False returns {jobProgressToken}. New executions always start with status UNEXECUTED. To carry over existing execution statuses and defect links from another cycle, use copy_executions_to_cycle instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cycle_idYes
projectYes
versionYes
issuesYes
assignee_typeNo
folder_idNo
waitNo
timeoutNo
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses new executions start as UNEXECUTED, async polling with wait, and that 'issues' can be list or comma-separated. It does not mention rate limits or auth, but is fairly transparent.

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 front-loaded with the core action. It uses bullet points and examples effectively, though slightly lengthy. It could be more concise but is well-structured.

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?

Given 8 parameters and no output schema, the description covers the main behavior, async feature, and key sibling differentiation. It does not describe the final payload but is sufficient for an experienced user.

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 0%, but description adds meaning for 'issues' format and 'wait' behavior. It mentions project/version accept keys/names or ids. However, it does not describe cycle_id, assignee_type, folder_id, timeout beyond defaults.

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 adds an explicit list of tests to a cycle as new UNEXECUTED executions. It uses specific verb 'add' and resource 'tests to cycle', and distinguishes from sibling 'copy_executions_to_cycle'.

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?

The description provides guidance on when to use this tool vs copy_executions_to_cycle (to carry over statuses). It explains the async behavior with wait parameter but does not explicitly state when not to use.

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/alejandroviera/zephyr-squad-server-mcp'

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