Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Get Test Plans

zephyr_get_test_plans
Read-onlyIdempotent

Retrieves test plan details from Zephyr, filtering by Jira project key, pagination, and update time to locate and review relevant testing plans.

Instructions

Get details of Test Plans in Zephyr

Toolset: Test Plans

Parameters:

  • projectKey (string): Jira project key 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 Plans

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

Expected Output: The first 10 Test Plans with their details

  1. Get any Test Plan

{
  "limit": 1
}

Expected Output: One Test Plan with its details

  1. Get five Test Plans starting from the ID 123

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

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

  1. Get one Test Plan from the project PROJ

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

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

  1. Get Test Plans updated after a given time

{
  "updatedAfter": "2024-01-01T00:00:00Z",
  "limit": 10
}

Expected Output: Up to 10 Test Plans updated after 2024-01-01 with their 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.
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?

The description adds useful behavioral context by disclosing that the server may enforce a lower limit, truncating results, and advises checking the limit field in the response. This goes beyond the annotations, which already indicate a safe read-only operation. It does not cover rate limits or error handling, but the annotations reduce that burden.

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 well-structured with headers and examples, but it repeats parameter descriptions already present in the schema, making it longer than necessary. The examples are useful, but the redundancy reduces conciseness. The front-loaded opening ensures the purpose is clear.

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?

The description covers main usage scenarios through examples and includes a note about truncation, which is important for API behavior. Since an output schema exists, return values don't need to be detailed. It doesn't explicitly mention whether projectKey is optional, but the examples imply that. Overall, it's sufficiently complete for a straightforward read-only list tool.

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?

The input schema already provides descriptions for all parameters, so the parameter details in the description are redundant. The examples add practical usage context, such as starting from an ID or filtering by projectKey, but they do not provide deeper semantic meaning beyond the schema. With 100% schema coverage, the baseline is 3, and the examples only slightly increase value.

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 opens with 'Get details of Test Plans in Zephyr', clearly stating the action, resource, and system. This distinguishes it from sibling tools like zephyr_get_test_cases by explicitly naming 'Test Plans'. The 'Toolset: Test Plans' heading reinforces the focus.

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 of parameter combinations but does not explicitly state when to use this tool over alternative Zephyr or QTM4J tools. Usage is implied by the tool's purpose, but there are no exclusions or alternatives mentioned. The examples show how to call the tool, not when to choose it.

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