Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Get Test Execution

zephyr_get_test_execution
Read-onlyIdempotent

Retrieve detailed information about a test execution using its numeric ID or alphanumeric key.

Instructions

Get details of test execution specified by id or key 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]+

Examples:

  1. Get the test execution with id 1

{
  "testExecutionIdOrKey": "1"
}

Expected Output: The test execution with its details

  1. Get the test execution with key 'PROJ-E123'

{
  "testExecutionIdOrKey": "PROJ-E123"
}

Expected Output: The test execution with its details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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
idYesThe ID of the entity
keyNoTest execution key
linksNo
commentNoComment added against overall test case execution.
projectYesID and link relative to Zephyr project.
testCaseYes
automatedNoIndicates if the test execution was done manually or not.
testCycleNo
environmentNoID and link to the environment resource.
assignedToIdNoAtlassian Account ID of the Jira user.
customFieldsNoMulti-line text fields support HTML and should denote new lines with the \<br\> tag. Dates should be in the format 'yyyy-MM-dd'. Users should have values of Jira User Account IDs.
executedByIdNoAtlassian Account ID of the Jira user.
actualEndDateNoThe actual end date of the test cycle. Format: yyyy-MM-dd'T'HH:mm:ss'Z'
estimatedTimeNoEstimated duration in milliseconds.
executionTimeNoActual test execution time in milliseconds.
jiraProjectVersionNoID and Link to fetch information about Jira Project version. Relates to 'Version' or 'Releases' in Jira projects.
testExecutionStatusYesID and link to the status resource.
Behavior3/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint, covering safety and idempotency. The description adds no behavioral detail beyond the schema's parameter format. It does not contradict annotations, but adds minimal value beyond them.

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 concise, front-loaded with purpose, and includes examples. The 'Toolset' heading is useful but adds minimal length. Could be slightly more efficient by removing redundant parameter description, but overall well-structured.

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 tool's low complexity (single required parameter, read-only, idempotent), the description covers essential aspects. An output schema exists (not shown), so return values need not be detailed. No mention of error cases or rate limits, but not critical for this simple operation.

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%, so baseline is 3. The description largely repeats the schema's parameter description, adding only an example key format (e.g., 'PROJ-E123') and the pattern text, which do not significantly enhance understanding beyond the schema.

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 action ('Get details') and the resource ('test execution specified by id or key'). It distinguishes from siblings like 'zephyr_get_test_executions' (plural) which retrieves a list, making the tool's specific purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives such as 'zephyr_get_test_executions' for lists or 'zephyr_get_test_execution_steps' for steps. The description assumes the user will infer from the name, but lacks explicit contextual cues or exclusions.

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