Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

QTM4J: Update Test Step Execution

qtm4j_update_test_step_execution
Idempotent

Update a test step's execution result, actual result, or comment in a SmartBear qTest cycle by providing test cycle key, test case key, and step sequence number.

Instructions

Update a test step execution (execution result, actual result, comment). Looks up testStepExecutionId from testCycleKey, testCaseKey, and step sequence number; resolves executionResultId name to a numeric ID.

Toolset: Test Executions

Parameters:

  • testCycleKey (string) required: Test cycle key in the format '{PROJECT_KEY}-TR-{number}', e.g. 'SCRUM-TR-101'. Used directly as the API path parameter.

  • testCaseKey (string) required: Test case key in the format '{PROJECT_KEY}-TC-{number}', e.g. 'SCRUM-TC-145'.

  • testStepSeqNo (number) required: sequence number of the step to update (e.g. 2 = the second step).

  • executionResultId (string): Execution result name, e.g. 'Pass', 'Fail', 'Blocked', 'In Progress', 'Not Executed'. Project-specific (custom results allowed); resolved case-insensitively to a numeric executionResultId.

  • comment (string): Step execution comment. Pass null to clear the existing comment.

  • actualResult (string): Actual result for this test step. Set to null to clear the existing value.

Output Description: Confirmation object with testCycleKey, testCaseKey, testStepSeqNo, and updated: true. executionResultName is included when the server returns it. Warnings are returned in content if executionResultId name could not be resolved.

Use Cases: 1. Set a test step execution result (e.g. Pass, Fail, Blocked) 2. Update actualResult or comment on a test step execution

Examples:

  1. Mark step 2 as Pass

{
  "testCycleKey": "PROJ-TR-101",
  "testCaseKey": "PROJ-TC-42",
  "testStepSeqNo": 2,
  "executionResultId": "Pass"
}

Expected Output: { testCycleKey: 'PROJ-TR-101', testCaseKey: 'PROJ-TC-42', testStepSeqNo: 2, executionResultName: 'Pass', updated: true }

  1. Update step 3 with actualResult and comment

{
  "testCycleKey": "PROJ-TR-101",
  "testCaseKey": "PROJ-TC-42",
  "testStepSeqNo": 3,
  "executionResultId": "Fail",
  "actualResult": "Button not found on page.",
  "comment": "Reproduced consistently in Chrome."
}

Expected Output: { testCycleKey: 'PROJ-TR-101', testCaseKey: 'PROJ-TC-42', testStepSeqNo: 3, executionResultName: 'Fail', updated: true }

  1. Clear actualResult on step 1

{
  "testCycleKey": "PROJ-TR-101",
  "testCaseKey": "PROJ-TC-42",
  "testStepSeqNo": 1,
  "actualResult": null
}

Expected Output: { testCycleKey: 'PROJ-TR-101', testCaseKey: 'PROJ-TC-42', testStepSeqNo: 1, updated: true }

Hints: 1. Call set_project_context before this tool. 2. At least one updatable field must be provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commentNoStep execution comment. Pass null to clear the existing comment.
testCaseKeyYesTest case key in the format '{PROJECT_KEY}-TC-{number}', e.g. 'SCRUM-TC-145'.
actualResultNoActual result for this test step. Set to null to clear the existing value.
testCycleKeyYesTest cycle key in the format '{PROJECT_KEY}-TR-{number}', e.g. 'SCRUM-TR-101'. Used directly as the API path parameter.
testStepSeqNoYessequence number of the step to update (e.g. 2 = the second step).
executionResultIdNoExecution result name, e.g. 'Pass', 'Fail', 'Blocked', 'In Progress', 'Not Executed'. Project-specific (custom results allowed); resolved case-insensitively to a numeric executionResultId.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
updatedYesTrue when the server confirms the update (HTTP 200 OK) and the test step execution is successfully updated.
testCaseKeyYesKey of the test case whose step execution was updated (e.g. 'SCRUM-TC-145').
testCycleKeyYesKey of the test cycle containing the updated step execution (e.g. 'SCRUM-TR-101').
testStepSeqNoYessequence number of the test step whose execution was updated.
executionResultNameNoName of the execution result applied to the step (e.g. 'Pass', 'Fail'). Present only when the server returns it.
Install Server

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses meaningful behavior: it 'looks up testStepExecutionId' from keys and sequence number, resolves executionResultId names case-insensitively to numeric IDs including project-specific custom results, and warns that unresolved names are surfaced in content. It also specifies null-clearing semantics for comment and actualResult, and includes output examples showing the confirmation shape.

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 longer than average but well-structured with sections for Toolset, Parameters, Output, Use Cases, Examples, and Hints. The main verb and resource are front-loaded. While the parameter list duplicates schema content somewhat, the examples and behavioral notes justify the length.

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?

The description is complete for a moderate-complexity update tool: it specifies required context (set_project_context), minimum input requirements (at least one updatable field), lookup logic, output confirmation fields, warning behavior, and concrete examples. With an output schema present and no nested objects, an agent has everything needed to invoke it correctly.

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?

Schema coverage is 100%, so the schema already documents all parameters. The description adds valuable semantics such as 'Used directly as the API path parameter', the project-specific and case-insensitive resolution of executionResultId, and null-to-clear behavior. Examples illustrate realistic parameter combinations, which pushes this above the baseline.

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 opens with a specific verb and resource: 'Update a test step execution (execution result, actual result, comment)', which immediately distinguishes it from test case execution updates. It also explains the lookup path through testCycleKey, testCaseKey, and step sequence number, removing ambiguity about which entity is modified.

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 'Use Cases' section clearly states the two intended scenarios: setting an execution result and updating actualResult/comment. The hint 'Call set_project_context before this tool' provides a necessary precondition, and 'At least one updatable field must be provided' gives a practical guardrail. It does not explicitly name alternatives or when not to use this tool, but the context is sufficiently clear.

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