Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Get Test Cycles

zephyr_get_test_cycles
Read-onlyIdempotent

Retrieve test cycle details from Zephyr using filters for project, folder, or version. Supports pagination to control result size.

Instructions

Get details of Test Cycles in Zephyr

Toolset: Test Cycles

Parameters:

  • projectKey (string): Jira project key filter

  • folderId (number): Folder ID filter

  • jiraProjectVersionId (number): Jira Project Version ID. Relates to 'Version' or 'Releases' in Jira projects.

  • maxResults (number): Specifies the maximum number of results to return in a single call. The default value is 10, and the maximum value that can be requested is 1000.

Note that the server may enforce a lower limit than requested, depending on resource availability or other internal constraints. If this happens, the result set may be truncated. Always check the maxResults value in the response to confirm how many results were actually returned. (default: 10)

  • startAt (number): Zero-indexed starting position. Should be a multiple of maxResults. (default: 0)

Examples:

  1. Get the first 10 Test Cycles

{
  "maxResults": 10,
  "startAt": 0
}

Expected Output: The first 10 Test Cycles with their details

  1. Get any Test Cycle

{
  "maxResults": 1
}

Expected Output: One Test Cycle with its details

  1. Get five Test Cycles starting from the 7th Test Cycles of the list

{
  "maxResults": 5,
  "startAt": 6
}

Expected Output: The 7th to the 11th Test Cycles with their details

  1. Get one Test Cycle from the project PROJ

{
  "projectKey": "PROJ",
  "maxResults": 1
}

Expected Output: One Test Cycle from project PROJ with its details

  1. Get one Test Cycle from the folder with ID 123

{
  "folderId": 123,
  "maxResults": 1
}

Expected Output: One Test Cycle from folder with ID 123 with its details

  1. Get one Test Cycle from the version 456

{
  "jiraProjectVersionId": 456,
  "maxResults": 1
}

Expected Output: One Test Cycle from version 456 with its details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startAtNoZero-indexed starting position. Should be a multiple of maxResults.
folderIdNoFolder ID filter
maxResultsNoSpecifies the maximum number of results to return in a single call. The default value is 10, and the maximum value that can be requested is 1000. Note that the server may enforce a lower limit than requested, depending on resource availability or other internal constraints. If this happens, the result set may be truncated. Always check the maxResults value in the response to confirm how many results were actually returned.
projectKeyNoJira project key filter
jiraProjectVersionIdNoJira Project Version ID. Relates to 'Version' or 'Releases' in Jira projects.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nextNoURL to the next page of results, or null if there are no more results.
totalNoIndicates the total number of items available across all pages.
isLastNoIndicates if this is the last page of results.
valuesNo
startAtYesIndicates the index of the first item returned in the page of results.
maxResultsYesIndicates the maximum number of results in this response. Note that the server may enforce a lower limit than requested, depending on resource availability or other internal constraints.
Behavior4/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context about pagination: the server may enforce a lower limit than requested, and to always check the maxResults value in the response. 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.

Conciseness3/5

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

The description is front-loaded with purpose and toolset, but includes redundant parameter descriptions already present in the schema. The examples are helpful but could be trimmed to avoid repetition.

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 that annotations are complete, an output schema exists, and schema coverage is full, the description adequately covers pagination behavior and filter options. It does not explain return values, but the output schema fills that gap.

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% with descriptions. The description repeats parameter info but adds practical context through six examples that demonstrate parameter usage and expected outputs, which adds meaning beyond the schema.

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 'Get details of Test Cycles in Zephyr', using a specific verb and resource. This distinguishes it from sibling tools like zephyr_create_test_cycle and zephyr_get_test_cycle.

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?

The description provides examples showing usage with various filters, but lacks explicit guidance on when to use this tool versus alternatives like zephyr_get_test_cycle (singular) or other test cycle tools. Usage is implied through examples but not stated outright.

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