Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Get priorities

zephyr_get_priorities
Read-onlyIdempotent

Retrieve Zephyr test case priorities with optional filters for project key, result count, and starting position.

Instructions

Get Zephyr Test Case priorities with optional filters

Toolset: Priorities

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

Examples:

  1. Get the first 10 priorities

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

Expected Output: The first 10 priorities with their details

  1. Get priorities for a specific project

{
  "projectKey": "PROJ"
}

Expected Output: The priorities for project PROJ

  1. Get all priorities

{}

Expected Output: All priorities

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

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 indicate read-only, idempotent, and non-destructive behavior. The description adds valuable context about pagination behavior (server may enforce lower limit, response may be truncated) and the need to check 'maxResults' in the response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is well-structured: purpose, toolset, parameters with details and notes, followed by examples. Every section is concise and informative, with no wasted text.

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?

With an output schema present, return value explanation is not needed. The description covers pagination, filtering, and provides examples. It is complete for a simple read operation.

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 already documents parameters. The description adds value by providing examples showing parameter usage together, and a note about maxResults being possibly capped by the server.

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 Zephyr Test Case priorities with optional filters', identifying the action, resource, and scope. It differentiates from sibling tools like 'zephyr_get_environments' or 'zephyr_get_statuses' by specifying 'priorities'.

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. While the purpose is clear, the description lacks when-not-to-use instructions or comparisons to other Zephyr tools, such as other get tools.

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