Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Create Test Case Steps

zephyr_create_test_case_steps
Destructive

Add or replace test case steps in Zephyr with inline instructions or delegation to another test case.

Instructions

Create steps for a Test Case in Zephyr. Supports inline step definitions or delegating execution to another test case (also known as 'call to test' via UI). Requires a mode: APPEND adds steps to the end of the existing list, OVERWRITE deletes all existing steps and replaces them with the provided ones. Always ask the user to choose between OVERWRITE or APPEND before calling this tool.

Toolset: Test Cases

Examples:

  1. To the Test Case SA-T1, add steps that will test a login page.

{
  "testCaseKey": "SA-T1",
  "mode": "APPEND",
  "items": [
    {
      "inline": {
        "description": "Navigate to the login page",
        "expectedResult": "Login page is displayed"
      }
    },
    {
      "inline": {
        "description": "Enter valid credentials and click Submit",
        "expectedResult": "User is redirected to the dashboard"
      }
    }
  ]
}

Expected Output: The ID of the Test Steps resource and the API self URL to fetch it

  1. To the Test Case MM2-T15, replace all existing steps with new ones that test the settings page for an Admin user.

{
  "testCaseKey": "MM2-T15",
  "mode": "OVERWRITE",
  "items": [
    {
      "inline": {
        "description": "Open the settings page",
        "testData": "User role: Admin",
        "expectedResult": "Settings page is accessible"
      }
    },
    {
      "inline": {
        "description": "Change the notification preference",
        "testData": "Preference: Email only",
        "expectedResult": "Notification preference is updated successfully"
      }
    }
  ]
}

Expected Output: The ID of the Test Steps resource and the API self URL to fetch it

  1. To the Test Case SA-T1, add a step that reuses the steps from the Test Case PRJ-T42

{
  "testCaseKey": "SA-T1",
  "mode": "APPEND",
  "items": [
    {
      "testCase": {
        "testCaseKey": "PRJ-T42"
      }
    }
  ]
}

Expected Output: The ID of the Test Steps resource and the API self URL to fetch it

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesValid values: `"APPEND"`, `"OVERWRITE"`. <br> `OVERWRITE` deletes and recreates the test steps and associated custom field values using the provided input. Attachments for existing steps are kept, but those for missing steps are deleted permanently <br> `APPEND` only adds extra steps to your test steps.
itemsYesThe list of test steps. Each step should be an object containing `inline` or `testCase`. **They should only include one of these fields at a time**.
testCaseKeyYesThe key of the test case. Test case keys are of the format [A-Z]+-T[0-9]+

Output Schema

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

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

Beyond the destructiveHint=true annotation, the description explicitly details the behavior: OVERWRITE deletes existing steps and replaces them, APPEND adds to the end, and attachments for missing steps are permanently deleted. No contradiction with annotations.

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 clear first sentence, followed by mode explanation, and three examples. It is slightly lengthy but every sentence adds value. Could be trimmed slightly, but overall efficient.

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?

Given the complexity (two step types, two modes), the description covers the main functionality, mode choice, and expected output. It lacks mention of error conditions or constraints (e.g., test case must exist), but the presence of an output schema (per context) reduces the need for return value details.

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?

With 100% schema coverage, baseline is 3. The description adds value by explaining the mode parameter's implications (e.g., data loss) and providing concrete examples for the items parameter, which clarify the structure beyond the schema descriptions.

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 steps for a test case, distinguishes between inline and call-to-test options, and explicitly defines the two modes (APPEND/OVERWRITE). This differentiates it clearly from sibling tools like zephyr_get_test_case_steps (read-only) or zephyr_create_test_case (different resource).

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 description instructs the agent to ask the user to choose between OVERWRITE and APPEND before calling, explaining when each mode is appropriate. It provides examples covering both modes and step types. However, it does not explicitly state when not to use this tool (e.g., for updating existing steps) or mention prerequisites like test case existence.

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