Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Get Test Plans

zephyr_get_test_plans
Read-onlyIdempotent

Fetch Test Plans from Zephyr with filters for project, pagination, and recent updates to get detailed plan information.

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
Install Server

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description does not contradict them. It adds valuable behavioral context by warning that 'the server may enforce a lower limit than requested' and advising the agent to 'Always check the limit value in the response', which clarifies possible result truncation.

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 sections for toolset, parameters, and examples, and it front-loads the purpose. However, it is longer than necessary: the parameter definitions duplicate the schema, and the five examples with 'Expected Output' lines are repetitive and could be trimmed.

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, idempotent list operation with an output schema and rich annotations, the description covers all essential call details: filters, defaults, pagination, date format, and the truncation caveat. The examples further clarify usage, and the output schema removes the need to describe return values in prose.

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 description coverage is 100%, so the baseline is 3. The description repeats the schema's parameter docs but adds value through five concrete examples showing valid parameter combinations and expected outcomes, such as using startAtId for ID-based pagination and projectKey for project filtering.

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 opens with a specific action and resource: 'Get details of Test Plans in Zephyr', reinforced by the 'Toolset: Test Plans' label. It is distinct from sibling tools like zephyr_get_test_cycles and zephyr_get_test_cases, though it does not explicitly state the comparison.

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 numerous examples showing parameter combinations, such as 'Get five Test Plans starting from the ID 123' and 'Get Test Plans updated after a given time', which implies usage. However, it never explicitly states when to choose this tool over alternative sibling tools for test cycles or test cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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