Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

QTM4J: Unlink Test Cases from Requirement

qtm4j_unlink_test_cases_from_requirement

Unlink test cases from a Jira requirement in QTM4J by specifying test case keys or filter criteria. Clean up traceability links and remove stale or incorrect test case associations.

Instructions

Unlink test cases from a Jira requirement in QTM4J by test case keys or filter criteria. Test case keys are resolved to internal IDs automatically.

Toolset: Requirements

Parameters:

  • requirementKey (string) required: Jira requirement key (e.g., 'SCRUM-1'). Resolved to the internal Jira issue ID automatically.

  • testCaseKeys (array): Test case keys to unlink (e.g., ['SCRUM-TC-1', 'SCRUM-TC-2']). Resolved to internal IDs and latest versions automatically. Provide this OR filter — not both.

  • filter (object): Filter criteria to select test cases to unlink. Use instead of testCaseKeys when selecting by criteria. projectId is auto-filled from the active project context.

Output Description: Confirmation with the requirement key and unlinked: true. Warnings included if any test cases could not be resolved or unlinked.

Use Cases: 1. Remove specific test cases from a Jira requirement 2. Unlink test cases matching a filter from a requirement 3. Clean up stale or incorrect test case links on a requirement 4. Remove traceability links as part of sprint cleanup

Examples:

  1. Unlink specific test cases by key

{
  "requirementKey": "SCRUM-1",
  "testCaseKeys": [
    "SCRUM-TC-10",
    "SCRUM-TC-11"
  ]
}

Expected Output: Test cases unlinked from requirement SCRUM-1

  1. Unlink test cases matching a filter

{
  "requirementKey": "SCRUM-1",
  "filter": {
    "status": [
      "Done"
    ],
    "labels": [
      "Deprecated"
    ]
  }
}

Expected Output: Filtered test cases unlinked from requirement

Hints: 1. PREREQUISITE: set_project_context must be called before this tool. NEVER auto-select a project. 2. REQUIREMENT KEY FORMAT: '{PROJECT_KEY}-{number}' — e.g. 'SCRUM-1'. 3. TEST CASE KEY FORMAT: '{PROJECT_KEY}-TC-{number}' — e.g. 'SCRUM-TC-145'. 4. Provide either testCaseKeys or filter — not both. 5. projectId in filter is auto-filled from the active project context — do not set it manually. 6. filter.excludeTestCases can be used to exclude specific test cases when using filter-based unlinking. 7. If a test case key cannot be resolved, it is reported in warnings and other test cases are still unlinked.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoFilter criteria to select test cases to unlink. Use instead of testCaseKeys when selecting by criteria. projectId is auto-filled from the active project context.
testCaseKeysNoTest case keys to unlink (e.g., ['SCRUM-TC-1', 'SCRUM-TC-2']). Resolved to internal IDs and latest versions automatically. Provide this OR filter — not both.
requirementKeyYesJira requirement key (e.g., 'SCRUM-1'). Resolved to the internal Jira issue ID automatically.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkedNo
unlinkedNo
requirementKeyYes
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), it discloses key-resolution behavior ('Resolved to internal IDs and latest versions automatically'), partial-failure semantics ('other test cases are still unlinked'), warning output, and the auto-filled projectId behavior. This is exactly the behavioral context an agent needs before invoking a link-mutation tool.

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 long, but it is divided into clear sections (toolset, parameters, output, use cases, examples, hints) with no filler. A bit of redundancy with the schema remains, and the 7 hints plus 4 use cases could be tightened, so it does not reach the concise ideal of a 5.

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 tool with a complex filter object and a mutation side effect, the description covers prerequisites, key formats, parameter exclusivity, output shape, warnings, and examples. An agent has everything needed to decide when and how to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already documents all three parameters, the description adds the exclusive-OR relationship between testCaseKeys and filter, auto-resolution details, key formats, excludeTestCases capability, and complete JSON examples for both parameter paths. This materially exceeds the schema's bare descriptions.

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 opening sentence names a specific verb ('Unlink') and resource ('test cases from a Jira requirement') and adds selection methods ('by test case keys or filter criteria'). This clearly distinguishes it from the sibling qtm4j_link_test_cases_to_requirement and the inverse qtm4j_unlink_requirements_from_test_case.

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?

It gives explicit in-tool guidance: 'Provide this OR filter — not both', tells users to prefer filter when selecting by criteria, and lists a hard prerequisite ('set_project_context must be called before this tool'). It does not name alternative sibling tools for mutually exclusive decisions, so it stops short of 5.

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