Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Get Test Cycle

zephyr_get_test_cycle
Read-onlyIdempotent

Retrieve detailed information about a Zephyr test cycle using its ID or key.

Instructions

Get details of test cycle specified by id or key in Zephyr

Toolset: Test Cycles

Parameters:

  • testCycleIdOrKey (string) required: The ID or key of the test cycle.

Examples:

  1. Get the test cycle with id 1

{
  "testCycleIdOrKey": "1"
}

Expected Output: The test cycle with its details

  1. Get the test cycle with key 'SA-R40'

{
  "testCycleIdOrKey": "SA-R40"
}

Expected Output: The test cycle with its details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
testCycleIdOrKeyYesThe ID or key of the test cycle.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the entity
keyYesUnique key of the test cycle
nameYesName of the Test Cycle
linksNoRepresents all links that a Test Cycle has.
ownerNo
folderNoID and link to the folder resource.
statusYesID and link to the status resource.
projectYesID and link relative to Zephyr project.
descriptionNoDescription outlining the scope.
customFieldsNoMulti-line text fields support HTML and should denote new lines with the \<br\> tag. Dates should be in the format 'yyyy-MM-dd'. Users should have values of Jira User Account IDs.
plannedEndDateNoThe planned end date of the test cycle. This field cannot be blank. Setting it as null or excluding it from the request will leave the field values unchanged. ISO 8601 Format (i.e., yyyy-MM-dd'T'HH:mm:ss'Z')
plannedStartDateNoPlanned start date of the test cycle. This field cannot be blank. Setting it as null or excluding it from the request will leave the field values unchanged. ISO 8601 Format (i.e., yyyy-MM-dd'T'HH:mm:ss'Z')
jiraProjectVersionNoID and Link to fetch information about Jira Project version. Relates to 'Version' or 'Releases' in Jira projects.
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds minimal behavioral context beyond 'details'. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is short and front-loaded with the action and resource. The toolset and parameter labels are somewhat redundant but not harmful. Examples are clear and beneficial.

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?

For a simple retrieval tool with one well-documented parameter and an output schema, the description provides sufficient context. Missing details like error handling are minor given the tool's simplicity.

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 100%, and the description merely restates the parameter name and pattern without adding deeper meaning or format constraints.

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 action ('Get details') and the resource ('test cycle specified by id or key'), distinguishing it from siblings like `zephyr_get_test_cycles` which retrieves multiple cycles.

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?

No explicit guidance on when to use this tool versus alternatives like `zephyr_get_test_cycles` or `zephyr_get_test_cycle_links`. The examples are useful but do not clarify selection criteria.

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/SmartBear/smartbear-mcp'

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