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 detailed steps of a test execution, with options to paginate results, start at a specific position, or filter by test data row.

Instructions

Get details of test execution steps in Zephyr

Toolset: Test Executions

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.
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, indicating a safe read operation. The description adds examples but no extra behavioral traits beyond what the schema and annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description starts with a clear purpose line, but contains many lengthy examples that could be condensed. The structure is front-loaded but not optimally concise.

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 output schema exists and the tool has 4 parameters, the description covers pagination (startAt, maxResults) and testDataRowNumber with multiple examples. It is fairly complete for a read-only retrieval tool.

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 description coverage is 100% (all 4 parameters have descriptions). The description adds no additional semantic meaning beyond the schema; examples illustrate usage but do not enhance parameter understanding.

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 'Get' and the resource 'test execution steps'. It distinguishes from sibling tools like zephyr_get_test_execution (which gets the execution itself) and zephyr_update_test_execution_steps (update step details).

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 includes a 'Toolset: Test Executions' heading and many examples, but does not explicitly state when to use this tool vs alternatives or when not to use it. Usage is implied through examples.

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