jira-xray-cloud-mcp

Xray Update Test Definition

xray_update_test_definition

Idempotent

Update a Jira Xray Test by replacing its Gherkin scenario or unstructured definition; for manual tests, use the step tools.

Instructions

Replace the Gherkin or unstructured definition of a Test. Use the step tools for manual tests.

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": {
      "test": "<test>"
    },
    "name": "xray_update_test_definition"
  }
}

Input Schema

Name	Required	Description
`test`	Yes	Jira issue key (e.g. 'CALC-12') or numeric issue id.
`gherkin`	No	New Gherkin scenario (Cucumber tests).
`version_id`	No	Test version id; default is the current version.
`unstructured`	No	New free-text definition (Generic tests).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The word 'Replace' usefully signals that the existing definition is overwritten, but the description adds nothing about permissions, what happens on partial input, or how versioning interacts with the update.

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?

Two short sentences with zero filler, and the core action is front-loaded ahead of the routing hint. Every clause earns its place.

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?

The tool is a mutation with an output schema and full parameter coverage, so the description need not explain returns. However, it omits whether gherkin and unstructured are mutually exclusive, how they relate to the test type, and version_id behavior, leaving meaningful gaps for an update tool.

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 the schema already documents test, gherkin, version_id, and unstructured. The description's mention of 'Gherkin or unstructured' mirrors the schema rather than adding format details, mutual-exclusivity rules, or guidance on version_id. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Replace') and resource ('the Gherkin or unstructured definition of a Test'), so the agent knows exactly what is being modified. It does not name a sibling tool explicitly, but the phrase 'step tools' points away from the step-related siblings.

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?

Provides a clear when-not with an alternative category: 'Use the step tools for manual tests.' That routes the agent away from this tool for manual/step-based tests. It stops short of explicitly naming xray_update_test_step or telling the agent which of gherkin vs unstructured to pick.

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

Deploy Server