Skip to main content
Glama

jira_get_project_versions

Retrieves all versions defined in a Jira project, including names, release status, and dates, to find Fix Version values and support release planning.

Instructions

Get all versions (releases) defined in a Jira project. Returns version names, release status, and dates. Useful for finding Fix Version values when creating/updating issues or for release planning.

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": {
      "projectKey": "<projectKey>"
    },
    "name": "jira_get_project_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectKeyYesProject key (e.g., KP)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the load; it does disclose what comes back (version names, release status, dates), which is valuable given there is no output schema. It is silent on permissions, pagination, and whether archived or unreleased versions are included, which are the main behavioral unknowns for this call.

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?

Three tight sentences with the core purpose front-loaded and no filler. Nothing is wasted, though the return-value sentence and the usage sentence could be slightly compressed.

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

Completeness4/5

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

For a one-parameter read tool with no output schema, the description covers purpose, return contents, and typical use. The gaps are minor: pagination behavior and whether archived versions appear, both of which an agent may want before relying on the list.

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 coverage is 100% with a single required projectKey that the schema already documents with an example ('KP'). The description only implies project scoping and adds no format or edge-case detail about the key beyond what the schema provides.

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?

The description gives a specific verb and resource ('Get all versions (releases) defined in a Jira project'), clarifying that 'versions' means releases. It is distinguishable from jira_create_version and jira_get_project by the read-only, version-listing scope, though it never explicitly contrasts with a sibling.

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?

It gives concrete use cases: finding Fix Version values when creating/updating issues, and release planning. That tells an agent the situations this tool serves, but there are no exclusions or named alternatives for cases like fetching issue fields or transitions.

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