Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

QTM4J: Unlink Test Cases from Test Cycle

qtm4j_unlink_test_cases_from_test_cycle

Remove test cases from a QTM4J test cycle by keys, filter criteria, or unlink all at once. Clean up cycles before repopulating them.

Instructions

Unlink test cases from a QTM4J test cycle by test case keys, filter criteria, or all at once with unlinkAll.

Toolset: Test Cycles

Parameters:

  • cycleKey (string) required: Test Cycle key (e.g., 'SCRUM-TR-1'). Resolved to the internal cycle UID 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 or unlinkAll — not combined.

  • unlinkAll (boolean): If true, all test cases are unlinked from the cycle. Ignores testCaseKeys and filter.

  • filter (object): Filter criteria to select test cases to unlink. projectId is auto-filled from the active project context.

Output Description: Confirmation with the cycle 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 test cycle by key 2. Unlink all test cases from a test cycle at once 3. Remove test cases matching a filter from a cycle (e.g., all 'Done' test cases) 4. Clean up a test cycle before repopulating it

Examples:

  1. Unlink two specific test cases

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

Expected Output: Test cases unlinked from test cycle

  1. Unlink all test cases from a cycle

{
  "cycleKey": "SCRUM-TR-1",
  "unlinkAll": true
}

Expected Output: All test cases unlinked from cycle

  1. Unlink test cases matching a status filter

{
  "cycleKey": "SCRUM-TR-5",
  "filter": {
    "status": [
      "Done"
    ],
    "labels": [
      "Deprecated"
    ]
  }
}

Expected Output: Filtered test cases unlinked from cycle

Hints: 1. PREREQUISITE: set_project_context must be called before this tool. NEVER auto-select a project. 2. CYCLE KEY FORMAT: '{PROJECT_KEY}-TR-{id}' — e.g. 'SCRUM-TR-1'. Resolved to internal UID automatically. 3. TEST CASE KEY FORMAT: '{PROJECT_KEY}-TC-{number}' — e.g. 'SCRUM-TC-145'. 4. Provide exactly one of: testCaseKeys, unlinkAll, or filter. 5. unlinkAll: true removes every test case from the cycle — no need to list them individually. 6. projectId in filter is auto-filled from the active project context — do not set it manually. 7. If a test case key cannot be resolved, it is reported in warnings and others are still unlinked.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoFilter criteria to select test cases to unlink. projectId is auto-filled from the active project context.
cycleKeyYesTest Cycle key (e.g., 'SCRUM-TR-1'). Resolved to the internal cycle UID automatically.
unlinkAllNoIf true, all test cases are unlinked from the cycle. Ignores testCaseKeys and filter.
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 or unlinkAll — not combined.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkedNo
cycleKeyYes
unlinkedNo
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

The description adds meaningful behavioral context beyond the annotations: automatic resolution of keys to internal IDs and versions, unlinkAll ignoring the other parameters, projectId being auto-filled, and the important partial-failure behavior where unresolved keys are reported in warnings while other unlinking proceeds. This gives the agent a realistic model of how the tool executes.

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 long but well-structured into Purpose, Parameters, Output, Use Cases, Examples, and Hints. Every section serves a distinct purpose: prerequisites, key formats, selection modes, partial-failure behavior, and realistic invocation patterns. The front-loaded first sentence captures the core action immediately, and the examples are compact and directly actionable.

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 mutation tool with nested filter objects, required cycleKey, and multiple selection modes, the description is complete: it covers prerequisites, parameter constraints, output confirmation/warnings, and partial-failure semantics. The presence of an output schema reduces the need to explain return values, and the description still gives enough output context to set expectations.

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 description coverage is 100%, so the baseline is 3. The description adds real value on top with concrete key format examples, the mutual-exclusivity rule, the auto-resolution behavior, and three worked usage examples. Some of the parameter text duplicates schema descriptions, which prevents a 5, but the examples and hints make the parameter semantics substantially clearer.

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-resource pair: 'Unlink test cases from a QTM4J test cycle', and clarifies the three selection modes: keys, filter, or unlinkAll. This distinguishes it from sibling tools such as qtm4j_unlink_test_cases_from_requirement and qtm4j_link_test_cases_to_test_cycle by making both the action and the target resource explicit.

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 description provides clear usage context through Use Cases and Hints, including the explicit requirement to call set_project_context first and the rule to provide exactly one of testCaseKeys, unlinkAll, or filter. However, it does not explicitly name sibling alternatives or state when this tool should be preferred over them, so it falls just short of full routing guidance.

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