jira-xray-cloud-mcp

Xray Move To Folder

xray_move_to_folder

Idempotent

Move Xray Tests and Preconditions into a target folder within Test Repository or Test Plan folders, optionally setting their position.

Instructions

Move Tests (and, in the Test Repository, Preconditions) into a folder.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "xray_move_to_folder"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Folder path, e.g. '/Regression/API'. '/' is the root.
`index`	No	Position among sibling folders / issues.
`tests`	No	Test keys or ids.
`project`	No	Jira project key or id (for Test Repository folders).
`test_plan`	No	Test Plan key or id (for Test Plan folders instead of the repository).
`preconditions`	No	Precondition keys or ids (repository folders only).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already disclose the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true). The description adds one useful behavioral constraint—that Preconditions can only be moved in the Test Repository—but does not elaborate on permissions, side effects, or idempotency behavior beyond the annotations.

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 a single front-loaded sentence with no wasted words. It communicates the core action and scope efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has six parameters, an output schema, and rich annotations, the description is minimally adequate. It omits how tests can be moved into Test Plan folders (covered only by the schema), and lacks usage guidance, though the schema and annotations carry much of the burden.

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

Parameters3/5

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

Schema description coverage is 100%, so all six parameters are fully documented in the schema. The description does not add meaning beyond what the schema already provides (e.g., path format, index semantics, test_plan vs repository context).

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 states a specific verb ('Move'), the resources being moved ('Tests' and, conditionally, 'Preconditions'), and the destination ('into a folder'). This clearly distinguishes the tool from siblings like xray_move_folder (which moves folders) and xray_remove_from_folder (which removes items from folders).

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?

The description gives no explicit guidance on when to use this tool versus alternatives, nor does it state prerequisites, exclusions, or when-not-to-use conditions. The parenthetical about Preconditions being limited to the Test Repository provides some scope context, but no broader usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server