Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Create Folder

zephyr_create_folder

Create folders in a Zephyr project to organize test cases, test plans, or test cycles. Specify the project key, folder type, and name to structure testing artifacts.

Instructions

Create a folder called 'Axial Pump Tests' in the project SA for organizing test cases

Toolset: Folders

Parameters:

  • parentId (number): Folder ID of the parent folder. Must be null for root folders.

  • name (string) required: Folder name. Folder name must not contain / and \ characters.

  • projectKey (string) required: Jira project key.

  • folderType (string) required: Valid values: "TEST_CASE", "TEST_PLAN", "TEST_CYCLE"

Examples:

  1. Create a root Folder in project SA for organizing test cases

{
  "parentId": null,
  "name": "Axial Pump Tests",
  "projectKey": "SA",
  "folderType": "TEST_CASE"
}

Expected Output: The newly created Folder with its ID and self link

  1. Create a sub-folder under folder ID 5 in the project MM2 for test plans related to pumps

{
  "parentId": 5,
  "name": "Pump-related Test Plans",
  "projectKey": "MM2",
  "folderType": "TEST_PLAN"
}

Expected Output: The newly created Folder with its ID and self link

  1. Create a Folder called 'Regression Cycles' in project TIS for organizing test cycles

{
  "parentId": null,
  "name": "Regression Cycles",
  "projectKey": "TIS",
  "folderType": "TEST_CYCLE"
}

Expected Output: The newly created Folder with its ID and self link

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFolder name. Folder name must not contain `/` and `\` characters.
parentIdNoFolder ID of the parent folder. Must be `null` for root folders.
folderTypeYesValid values: `"TEST_CASE"`, `"TEST_PLAN"`, `"TEST_CYCLE"`
projectKeyYesJira project key.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe ID of the entity
selfNo
Behavior2/5

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

Annotations already indicate it's a write operation (readOnlyHint=false, destructiveHint=false). The description adds no new behavioral traits such as required permissions, idempotency, or side effects beyond the basic 'create' action.

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 well-structured with a parameter list and examples, but it starts with a very specific example which may be slightly distracting. Overall, it is efficient and front-loads the toolset and basic purpose.

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's complexity (4 parameters, output schema present), the description is complete: it explains all parameters, provides multiple examples, and notes expected output (ID and self link). It covers creation of root and sub-folders for various types.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds significant value by explaining each parameter in context (e.g., 'parentId' must be null for root folders, 'name' cannot contain certain characters, 'folderType' values). Three examples demonstrate correct 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?

The description clearly states the tool creates folders in Zephyr, with specific examples showing the verb 'create' and resource 'folder'. It distinguishes from siblings by focusing on folder creation (vs test cases, cycles, etc.) and describes folder types and root/sub-folder distinction.

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 does not explicitly state when to use this tool vs alternatives. While the examples imply usage scenarios, there is no direct guidance on when not to use it or which sibling tool might be more appropriate for a given task.

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