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

Unlink specific test cases from a QTM4J test cycle by keys, filter, or remove all at once to prepare the cycle for repopulation.

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
Behavior4/5

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

Annotations already indicate write operation; description adds auto-resolution of keys, handling of unresolved keys with warnings, and partial success behavior.

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?

Well-structured with sections, but somewhat verbose with examples and hints; still every part adds value.

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?

Given rich schema and output schema, description covers prerequisites, parameter constraints, output, and common scenarios completely.

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?

Despite 100% schema coverage, description adds crucial context: mutual exclusivity, auto-resolution, auto-fill of projectId, and format hints.

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?

Clearly states the tool unlinks test cases from a test cycle, specifies three methods (by keys, filter, all), and distinguishes from linking/searching siblings.

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

Usage Guidelines5/5

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

Explicitly states prerequisite (set_project_context), warns about mutual exclusivity of parameters, and provides use cases and examples.

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