mcp-xray

xray_import_execution_results

Import automated test execution results into Xray. Supports JUnit, NUnit, XUnit, Robot, TestNG, Cucumber, Behave, and JSON formats. Optionally specify a project or Test Execution issue.

Instructions

Imports automated test execution results into Xray. Supports formats: junit, nunit, xunit, robot, testng, cucumber, behave, json. Provide the full report content as a string. Optionally target a specific project or existing Test Execution issue.

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": {
      "format": "<format>",
      "reportContent": "<reportContent>"
    },
    "name": "xray_import_execution_results"
  }
}

Input Schema

Name	Required	Description
`format`	Yes	Format of the test report to import into Xray.
`projectKey`	No	Jira project key, e.g. 'OQA10', 'GAP'.
`testExecKey`	No	Key of an existing Test Execution issue to update, e.g. 'OQA10-42'.
`reportContent`	Yes	Full content of the test execution report as a string.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of disclosing side effects. It states 'Imports' (a mutation) but does not explain whether this creates a new Test Execution when no testExecKey is given, whether results are replaced or appended, or any permission/state-change details. The mention 'Optionally target... existing Test Execution issue' hints at behavior but is vague. This is a significant gap for a 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, with the main purpose front-loaded and supporting details following. Every sentence adds information: the supported formats and the required/optional inputs. There is no redundancy or wasted words.

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's moderate complexity (4 params, no output schema, no annotations), the description covers the essential usage: what formats are accepted and what to provide. However, it omits critical behavioral context such as the default behavior when no existing Test Execution key is provided (does it create a new one?), and it does not describe the return value or error scenarios. While an agent can likely invoke the tool correctly with the given information, the lack of these details makes it adequate but not thorough.

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 all four parameters. The description adds little beyond that: it repeats the format list (already an enum) and the concept of 'full report content'. It does clarify the purpose of projectKey and testExecKey ('target a specific project or existing Test Execution'), which is a minor addition, but overall the description does not significantly enhance understanding beyond the schema.

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 clearly states the action: 'Imports automated test execution results into Xray.' It lists supported formats and mentions targeting a specific project or existing Test Execution, distinguishing it from sibling tools like xray_create_test_execution which likely creates empty test executions. This is a specific verb+resource+target that differentiates the tool.

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 context: use this when you have a test report in one of the listed formats and want to bring it into Xray. It explains what to provide ('full report content as a string') and notes optional targets. However, it does not explicitly mention when NOT to use it or point to alternatives such as xray_create_test_execution for creating a new issue without results, so it falls short of a 5.

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

Deploy Server