Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Get Test Execution Steps

zephyr_get_test_execution_steps
Read-onlyIdempotent

Retrieve test execution steps from Zephyr for a given test execution ID or key, with optional pagination and test data row filtering to get specific step details.

Instructions

Get details of test execution steps in Zephyr

Toolset: Test Executions

Parameters:

  • testExecutionIdOrKey (string) required: The ID or key of the test execution. Test execution keys are of the format [A-Z]+-E[0-9]+

  • 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)

  • testDataRowNumber (number): The id of the test data row to retrieve.

Examples:

  1. Get the first 10 test execution steps for test execution with ID 1

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

Expected Output: The first 10 test execution steps with their details

  1. Get the first 10 test execution steps for test execution with key 'SA-E1'

{
  "testExecutionIdOrKey": "SA-E1",
  "maxResults": 10,
  "startAt": 0
}

Expected Output: The first 10 test execution steps with their details

  1. Get any test execution step for test execution with key 'SA-E1'

{
  "testExecutionIdOrKey": "SA-E1",
  "maxResults": 1
}

Expected Output: One test execution step with its details

  1. Get five test execution steps starting from the 7th test execution step for test execution with key 'SA-E1'

{
  "testExecutionIdOrKey": "SA-E1",
  "maxResults": 5,
  "startAt": 6
}

Expected Output: The 7th to the 11th test execution steps with their details

  1. Get test execution steps from the test data row 1 from test execution with key 'SA-E1'

{
  "testExecutionIdOrKey": "SA-E1",
  "testDataRowNumber": 1,
  "maxResults": 10,
  "startAt": 0
}

Expected Output: Test execution steps for the specified test data row

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.
testDataRowNumberNoThe id of the test data row to retrieve.
testExecutionIdOrKeyYesThe ID or key of the test execution. Test execution keys are of the format [A-Z]+-E[0-9]+

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.
valuesNoThe list of test steps
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

A3.7/5.0
Behavior4/5

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

Annotations already signal read-only, idempotent, and non-destructive behavior. The description adds meaningful behavioral context beyond that: the server may enforce a lower maxResults limit than requested, results may be truncated, and the caller should check the maxResults value in the response. This is useful, non-contradictory disclosure.

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 front-loaded with a clear one-line purpose and organized into Parameters and Examples sections. It is somewhat redundant with the schema's parameter descriptions, but the examples earn their place by illustrating pagination, startAt behavior, and testDataRowNumber usage.

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?

For a read-only paginated list operation with an output schema and full annotations, the description covers the key format, pagination caveat, startAt semantics, and test data row use cases well. The main completeness issue is the inconsistent maxResults limit between the description and the schema.

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?

All four parameters are fully described in the input schema, so the baseline is 3. The description restates those details and adds five worked examples showing valid combinations and expected outputs, which is helpful. However, it conflicts with the schema by claiming maxResults can be requested up to 1000 while the schema states a maximum of 9007199254740991, creating ambiguity for an agent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 details of test execution steps in Zephyr') and the Toolset label helps orient it within Test Executions. It does not explicitly distinguish itself from sibling tools like zephyr_get_test_case_steps or zephyr_get_test_execution, so an agent must infer those boundaries from the resource names.

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 examples show how to call the tool, and the purpose implies when it is appropriate, but there is no explicit 'use this instead of X' guidance or exclusionary context versus related Zephyr tools. Usage is implied rather than stated as clear decision criteria.

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