Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Get Statuses

zephyr_get_statuses
Read-onlyIdempotent

Retrieve statuses of test artifacts (test cases, plans, cycles, executions) in Zephyr. Filter by project key and status type with pagination.

Instructions

Get statuses of different types of test artifacts in Zephyr

Toolset: Statuses

Parameters:

  • 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)

  • projectKey (string): Jira project key filter

  • statusType (enum): Determines which type of entity the status belongs to.

Examples:

  1. Get the first 10 statuses

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

Expected Output: The first 10 statuses with their details from different projects and test artifact types

  1. Get 10 test case statuses

{
  "maxResults": 10,
  "statusType": "TEST_CASE"
}

Expected Output: A list of statuses related to test cases with their details

  1. Get five statuses from the project PROJ

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

Expected Output: The first five statuses from the project PROJ with their details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startAtNoZero-indexed starting position. Should be a multiple of maxResults.
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
statusTypeNoDetermines which type of entity the status belongs to.

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 already declare readOnlyHint and idempotentHint, indicating safe read operations. The description adds behavioral details about maxResults truncation and the need to check the response maxResults, which is valuable beyond the structured 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?

Well-organized with separate sections for description, parameters, and examples. The parameter notes are detailed but some repetition with schema exists. Overall clear and efficient despite a few redundant elements.

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 has 4 parameters, an enum, and an output schema, the description covers all necessary aspects including pagination, filtering, and practical usage through examples. The presence of an output schema means return values need not be described, making this complete.

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%, so the schema provides basic descriptions. The description adds value by elaborating on maxResults truncation and the relationship between startAt and maxResults, as well as providing concrete examples that illustrate parameter combinations.

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?

Title and description clearly state it retrieves statuses for test artifacts. The verb 'Get' and resource 'statuses' are specific, and the description distinguishes this tool from siblings by focusing on statuses rather than test cases or cycles.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/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 'get_test_case' or 'get_test_cycle'. The description shows parameter usage through examples but does not explain why one would choose this tool over others for retrieving status information.

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