Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Get Folders

zephyr_get_folders
Read-onlyIdempotent

Retrieve Zephyr folders by project and type to browse test case, plan, or cycle structures.

Instructions

Get folders, optionally filtered by project and folder type

Toolset: Folders

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

  • folderType (string): Folder type filter. Either "TEST_CASE", "TEST_PLAN" or "TEST_CYCLE"

Use Cases: 1. List folders in a Zephyr project 2. Get Test Case folders for a project 3. Get Test Plan folders for a project 4. Get Test Cycle folders for a project 5. Browse the folder structure in Zephyr

Examples:

  1. Get the first 10 Folders

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

Expected Output: The first 10 Folders with their details

  1. Get Folders from the project SA

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

Expected Output: Folders belonging to project SA with their details

  1. Get Test Case Folders from the project MM2

{
  "projectKey": "MM2",
  "folderType": "TEST_CASE",
  "maxResults": 10,
  "startAt": 0
}

Expected Output: Test Case Folders belonging to project MM2 with their details

  1. Get Test Cycle Folders across all projects

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

Expected Output: Test Cycle Folders from all projects with their details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startAtNoZero-indexed starting position. Should be a multiple of maxResults.
folderTypeNoFolder type filter. Either `"TEST_CASE"`, `"TEST_PLAN"` or `"TEST_CYCLE"`
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.
Install Server

TDQS

A4.4/5.0
Behavior4/5

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

The description adds behavioral context beyond the annotations by explaining that maxResults may be lowered by the server, results may be truncated, and the response's maxResults value should be checked. This is valuable for an agent handling pagination. Annotations already cover read-only/idempotent/non-destructive behavior, so the description supplements rather than replaces that information.

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?

The description is longer than minimal but well-structured with a one-sentence summary, parameter list, use cases, and examples. Each section earns its place, and the most important scoping information is front-loaded. It could be trimmed by removing duplication with the schema, but overall it is organized and readable.

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 that an output schema exists, annotations cover safety, and the description covers pagination, filtering behavior, and examples, the definition is complete for an agent to invoke this tool correctly. All four optional parameters are explained, and the examples cover both unfiltered and filtered calls.

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 baseline is 3, but the description goes further by showing parameter combinations in concrete examples with expected outputs, such as filtering by projectKey and folderType. It also repeats and clarifies the maxResults lower-bound behavior, which helps an agent apply the parameters correctly.

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 states a specific verb and resource: 'Get folders', and immediately clarifies optional filters by project and folder type. This distinguishes it from sibling tools like zephyr_get_projects or zephyr_get_test_cycles without requiring schema inspection. The Toolset heading reinforces its scope.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Use Cases' section provides clear scenarios such as listing folders in a project and filtering by folder type, giving an agent concrete context for when to call this tool. It does not explicitly mention alternatives or when not to use it, so it misses the top score, but the guidance is clear and actionable.

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