Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Create Test Script

zephyr_create_test_script

Creates plain text or BDD test scripts for Zephyr test cases, enabling step-by-step instructions or behavior-driven scenarios.

Instructions

Create a new Test Script of the types Plain Text or BDD in a Zephyr Test Case.

Toolset: Test Cases

Examples:

  1. Create a plain text test script for test case SA-T1 to verify that the axial pump can be enabled

{
  "testCaseKey": "SA-T1",
  "type": "plain",
  "text": "1. Navigate to Pump Settings</br>2. Enable Axial Pump</br>3. Verify pump status is 'Active'"
}

Expected Output: The created test script metadata including its id and self link

  1. Create a BDD test script for test case MM2-T15 to validate axial pump activation

{
  "testCaseKey": "MM2-T15",
  "type": "bdd",
  "text": "Given the axial pump is installed\nWhen the user enables the axial pump\nThen the pump status should be Active"
}

Expected Output: The created test script metadata including its id and self link

  1. Create a BDD test script for test case QA-T100 for axial pump performance validation

{
  "testCaseKey": "QA-T100",
  "type": "bdd",
  "text": "Given the system is running\nWhen the axial pump operates under load\nThen performance metrics should remain within thresholds"
}

Expected Output: The created test script metadata including its id and self link

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNo
typeNoTest scripts can be written in plain text or BDD format. The BDD type supports remote execution on a build system via API plugin. Supported Keywords for BDD: Given, When, Then, And, But. For more information about BDD and Gherkin syntax, see: https://support.smartbear.com/zephyr/docs/en/test-cases/gherkin-behavior-driven-development--bdd-.html For Plain Text scripts, we support HTML fragments. To create a step-by-step test script, you should use the POST /testcases/{testCaseKey}/teststeps endpoint.
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
Behavior3/5

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

Annotations indicate a write operation (readOnlyHint=false) and no idempotency or destructiveness. The description adds expected output (metadata with id and self link) but does not detail side effects like whether existing scripts are replaced or appended.

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?

Well-structured with a title, toolset label, and three clear examples. However, the examples are somewhat lengthy and could be more concise while still being helpful.

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?

Covers purpose, examples, and output schema. Lacks handling of edge cases like non-existent testCaseKey or pre-existing scripts, but is sufficient for typical creation scenarios.

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

Parameters3/5

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

Schema covers 67% of parameters with descriptions (testCaseKey and type get descriptions; text has only minLength). The description examples illustrate valid parameter combinations, but no additional semantic value beyond schema is provided in the main description.

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 verb 'Create' and the resource 'Test Script' within a Zephyr Test Case, specifying the types (Plain Text or BDD). It distinguishes from siblings like zephyr_create_test_case which creates a test case, not a script.

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?

Examples demonstrate common use cases, and the parameter description for 'type' mentions an alternative endpoint for step-by-step scripts. However, the main description lacks explicit guidance on when to choose this tool over others, such as creating test steps.

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