Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Get Test Executions

zephyr_get_test_executions
Read-onlyIdempotent

Retrieve test executions from Zephyr with filters for project, cycle, case, and date ranges. Supports pagination to control result set size.

Instructions

Get test executions with optional filters

Toolset: Test Executions

Parameters:

  • projectKey (string): Jira project key filter

  • testCycle (string): Test cycle key filter.

  • testCase (string): Test case key filter.

  • actualEndDateAfter (string): Filter for 'Actual End Date' after the given time. Format: yyyy-MM-dd'T'HH:mm:ss'Z'

  • actualEndDateBefore (string): Filter for 'Actual End Date' before the given time. Format: yyyy-MM-dd'T'HH:mm:ss'Z'

  • includeStepLinks (boolean): If true, execution step issue links will be included in the response (default: false)

  • jiraProjectVersionId (number): Jira Project Version ID. Relates to 'Version' or 'Releases' in Jira projects.

  • onlyLastExecutions (boolean): If true, includes only the last execution of each test cycle item (test case), and all ad-hoc test executions. (default: false)

  • limit (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 limit value in the response to confirm how many results were actually returned. (default: 10)

  • startAtId (number): Zero-indexed starting position for ID-based pagination. (default: 0)

  • updatedAfter (string): Filter only entities updated after the given time. Format: yyyy-MM-dd'T'HH:mm:ss'Z'

Examples:

  1. Get the first 10 test executions

{
  "limit": 10,
  "startAtId": 0
}

Expected Output: The first 10 test executions with their details

  1. Get 5 test executions for the project PROJ

{
  "projectKey": "PROJ",
  "limit": 5
}

Expected Output: Up to 5 test executions for project PROJ

  1. Get some test executions that finished after 01/Jan/2024

{
  "actualEndDateAfter": "2024-01-01T00:00:00Z"
}

Expected Output: Test executions that ended after 2024-01-01

  1. Get test executions with step links included

{
  "includeStepLinks": true
}

Expected Output: Test executions with step links included

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoSpecifies 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 limit value in the response to confirm how many results were actually returned.
testCaseNoTest case key filter.
startAtIdNoZero-indexed starting position for ID-based pagination.
testCycleNoTest cycle key filter.
projectKeyNoJira project key filter
updatedAfterNoFilter only entities updated after the given time. Format: yyyy-MM-dd'T'HH:mm:ss'Z'
includeStepLinksNoIf true, execution step issue links will be included in the response
actualEndDateAfterNoFilter for 'Actual End Date' after the given time. Format: yyyy-MM-dd'T'HH:mm:ss'Z'
onlyLastExecutionsNoIf true, includes only the last execution of each test cycle item (test case), and all ad-hoc test executions.
actualEndDateBeforeNoFilter for 'Actual End Date' before the given time. Format: yyyy-MM-dd'T'HH:mm:ss'Z'
jiraProjectVersionIdNoJira Project Version ID. Relates to 'Version' or 'Releases' in Jira projects.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nextNo
limitYes
valuesNo
nextStartAtIdYes
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is clear. The description adds useful behavioral details such as limit enforcement and pagination, but does not mention authentication or rate limits. At this level, it provides moderate additional context.

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 well-structured with sections for parameters, examples, and notes. It is somewhat verbose but all content is relevant. The front-loading of the core purpose is good, and examples are clearly formatted.

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 presence of an output schema (assumed to describe return values), the description adequately covers filtering, pagination, limit behavior, and common scenarios. It is sufficiently complete for a read-only, filtered list tool with no required parameters.

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 describes all parameters. The description adds value by grouping parameters, providing format examples, noting default values, and adding a critical note about server-enforced lower limits. The examples further illustrate usage.

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 clearly states 'Get test executions with optional filters', specifying the verb and resource. It does not explicitly differentiate from sibling tools like zephyr_get_test_execution (singular) or zephyr_get_test_executions_linked_to_a_jira_issue, but the purpose is unambiguous.

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?

Usage guidelines are implied through the description and examples, but there is no explicit guidance on when to use this tool versus alternatives (e.g., for a single execution vs. filtered list). The examples help but do not state conditions 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