Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Get Test Execution Links

zephyr_get_test_execution_links
Read-onlyIdempotent

Retrieve all links for a Zephyr test execution using its ID or key. Returns associated URLs and references.

Instructions

Get links for a specific test execution 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 links oftest execution with id 1

{
  "testExecutionIdOrKey": "1"
}

Expected Output: The test execution links with its details

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

{
  "testExecutionIdOrKey": "PROJ-E123"
}

Expected Output: The test execution links 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
selfNoThe REST API endpoint to get more resource details.
issuesNoA list of Jira issues linked to this entity
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds no behavioral context beyond the basic 'get' operation. It does not explain what type of links are returned or any additional side effects.

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

Conciseness5/5

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

The description is extremely concise, front-loading the purpose, and includes only essential information: toolset, parameter, and examples. Every sentence contributes meaning without redundancy.

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?

For a simple tool with one required parameter, complete output schema, and strong annotations, the description covers all necessary information. The examples demonstrate practical usage for both ID and key formats.

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%, and the description repeats the parameter definition but adds the format pattern and clear examples. This helps the agent understand the expected input format, adding value beyond the schema alone.

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 tool gets links for a specific test execution. The verb 'get' and resource 'links' are specific, and it distinguishes from sibling tools like get_test_execution (which gets execution details) and get_test_execution_steps.

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 guidance on when to use this tool versus alternatives like get_test_execution or get_test_execution_steps. The description does not mention exclusions or context, leaving the agent to infer usage from the name alone.

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