Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Get Test Cases

zephyr_get_test_cases
Read-onlyIdempotent

Retrieve test case details from Zephyr using filters like project key, folder ID, and update time. Supports pagination and returns up to 1000 results.

Instructions

Get details of test cases in Zephyr

Toolset: Test Cases

Parameters:

  • projectKey (string): Jira project key filter

  • folderId (number): Folder ID filter

  • limit (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 limit value in the response to confirm how many results were actually returned. (default: 10)

  • startAtId (number): Zero-indexed starting position for ID-based pagination. (default: 0)

  • updatedAfter (string): Filter only entities updated after the given time. Format: yyyy-MM-dd'T'HH:mm:ss'Z'

Examples:

  1. Get the first 10 Test Cases

{
  "limit": 10,
  "startAtId": 1
}

Expected Output: The first 10 Test Cases with their details

  1. Get any Test Case

{
  "limit": 1
}

Expected Output: One Test Case with its details

  1. Get five Test Cases starting from the ID 123

{
  "limit": 5,
  "startAtId": 123
}

Expected Output: Five Test Cases starting from the ID 123 with their details

  1. Get one Test Case from the project PROJ

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

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

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

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

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoSpecifies 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 limit value in the response to confirm how many results were actually returned.
folderIdNoFolder ID filter
startAtIdNoZero-indexed starting position for ID-based pagination.
projectKeyNoJira project key filter
updatedAfterNoFilter only entities updated after the given time. Format: yyyy-MM-dd'T'HH:mm:ss'Z'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nextNo
limitYes
valuesNo
nextStartAtIdYes
Behavior4/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds valuable behavioral context: the server may enforce a lower limit than requested, and the response's limit field should be checked for actual count. This goes beyond annotations by warning about truncation and pagination behavior.

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 begins with the purpose sentence, followed by parameter list and examples. This front-loads key information. However, the examples are extensive (5 blocks) and could be condensed. The parameter section duplicates schema descriptions, adding verbosity. Overall, could be more concise without losing clarity.

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 read-only list tool with an output schema (present but not shown), the description adequately covers input parameters, pagination behavior, and provides examples. It does not explain return values, but the output schema handles that. The toolset label aids discoverability. Missing details like sorting or default ordering are minor gaps.

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%, so the base score is 3. The description repeats parameter descriptions (e.g., limit, folderId, startAtId) but adds marginal value through examples that show parameter combinations. The behavioral note about limit truncation is also present in the schema. No new semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves details of test cases ('Get details of test cases in Zephyr'), with 'get' as verb and 'test cases' as resource. The plural form and parameters like limit and startAtId imply a list operation, distinguishing it from sibling tools like zephyr_get_test_case (singular). However, it does not explicitly state 'list' or 'search', leaving slight ambiguity.

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 examples demonstrate common parameter combinations and expected outputs, providing implicit usage guidance. However, the description does not explicitly state when to use this tool versus alternatives (e.g., zephyr_get_test_case for a single test case, or zephyr_get_test_cycles for cycles). There is no 'when not to use' or comparison to siblings.

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