jira-xray-cloud-mcp

Xray Get Test Plans

xray_get_test_plans

Read-onlyIdempotent

Search Xray Test Plans in Jira Cloud by JQL, keys, or project, with paginated results and selectable fields.

Instructions

Search Test Plans by JQL, keys or project (paginated).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "xray_get_test_plans"
  }
}

Input Schema

Name	Required	Description
`jql`	No	JQL filter.
`limit`	No	Page size (1-100).
`start`	No	Page offset (index of the first result).
`fields`	No	Jira fields to return in 'jira'. Default: ['key', 'summary', 'status', 'issuetype', 'project', 'assignee', 'labels'].
`project`	No	Jira project key or id.
`test_plans`	No	Restrict to these keys or ids.
`modified_since`	No	Only return issues modified after this date (ISO 8601, e.g. '2026-01-31').

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

B3.4/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 structurally. The description's only behavioral addition is 'paginated', which the limit/start schema parameters already convey, so it adds little beyond the structured data.

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?

One compact sentence with the resource and filter modes front-loaded and zero filler. It is appropriately sized, though the parenthetical '(paginated)' is somewhat redundant with the schema.

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?

An output schema exists so return values need no explanation, and annotations cover safety. However, for a 7-parameter collection tool sitting among many similarly named get_* tools, the description does not explain how jql, project, and test_plans interact or when to prefer one filter over another, leaving a modest gap.

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 each parameter (jql, project, test_plans, modified_since, fields, limit, start) is documented in the schema itself. The description adds no syntax or precedence detail beyond what the schema already provides, which is the baseline case.

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 (Test Plans) with the filter dimensions (JQL, keys, project) and pagination. It is clearly a bulk/collection query, contrasting with the singular xray_get_test_plan, though it never names that sibling explicitly.

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?

'Search' implies list/multi-result usage, which distinguishes it loosely from single-entity siblings, but there is no explicit when-to-use or when-not-to-use guidance and no mention of how it relates to xray_get_test_plan or the other get_* variants.

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

Deploy Server