jira-xray-cloud-mcp

Xray Get Tests

xray_get_tests

Read-onlyIdempotent

Search Xray Tests by JQL, keys, project, test type or Test Repository folder, with pagination and optional steps, definitions or requirements.

Instructions

Search Xray Tests by JQL, keys, project, test type or Test Repository folder (paginated).

Input Schema

TableJSON Schema

Name	Required	Description
`jql`	No	JQL filter, e.g. 'project = CALC AND labels = smoke'.
`limit`	No	Page size (1-100).
`start`	No	Page offset (index of the first result).
`tests`	No	Restrict to these Test keys or ids.
`fields`	No	Jira fields to return in 'jira'. Default: ['key', 'summary', 'status', 'issuetype', 'project', 'assignee', 'labels'].
`project`	No	Restrict to a Jira project (key or id).
`test_type`	No	Restrict to a test type name, e.g. 'Manual'.
`folder_path`	No	Restrict to a Test Repository folder path, e.g. '/Regression/API'.
`include_steps`	No	Include manual steps of each test.
`modified_since`	No	Only return issues modified after this date (ISO 8601, e.g. '2026-01-31').
`expand_call_tests`	No	Include steps with 'Call Test' steps replaced by the called Tests' steps (implies include_steps).
`include_definition`	No	Include Gherkin / unstructured definitions of each test.
`include_subfolders`	No	With folder_path: include descendant folders.
`include_requirements`	No	Also list the requirements (coverable issues) each Test covers.

Output Schema

TableJSON 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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds only the pagination trait, and says nothing about the expandable payload behavior the tool offers.

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?

A single front-loaded sentence with no filler; the search verb, the resource, the filter facets and the pagination caveat all appear in one pass.

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?

For a 14-parameter read tool with an output schema and rich annotations, the description is minimally adequate: it covers the search entry points but gives no hint that results can be enriched via include_steps, include_definition, expand_call_tests or include_requirements, which are meaningful behavioral choices an agent faces here.

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% and every parameter carries its own description (JQL example, page size/offset, field list default, folder path format), so the schema does the heavy lifting. The description's facet list largely restates schema content rather than adding syntax or interaction detail.

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 (Search) and resource (Xray Tests) plus the facets it can filter on, which cleanly separates it from the singular sibling xray_get_test and xray_get_expanded_test. It stops short of explicitly naming which sibling to use for a single-test lookup.

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

Usage Guidelines3/5

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

Usage is implied by the plural 'Search ... (paginated)' phrasing, which signals a list/multi-result retrieval, but the description never states when to prefer this over xray_get_test or xray_get_expanded_test, nor any prerequisite or exclusion.

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

Deploy Server