Skip to main content
Glama

jira_create_version

Create a new Jira project version or release for planning and tracking, with optional release status, dates, and description so issues can use it as a Fix Version.

Instructions

Create a new version/release in a Jira project for release planning and tracking. Versions can be used as Fix Version values on issues. Set released=true for already-released versions.

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": "<name>"
    },
    "name": "jira_create_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesVersion name (e.g., "v1.2.0", "Sprint 5", "Q1 2024")
releasedNoSet to true if this version has already been released
startDateNoDevelopment start date (YYYY-MM-DD format)
projectKeyYesProject key where the version will be created (e.g., KP)
descriptionNoDescription of what this version/release includes
releaseDateNoTarget or actual release date (YYYY-MM-DD format)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose that this is a creation operation and that released=true backdates an already-shipped version, which is genuinely useful. However, it says nothing about required permissions, what happens on duplicate names, or whether the call is idempotent — meaningful gaps 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.

Conciseness4/5

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

Three short sentences, front-loaded with the core action and ending on the one non-obvious parameter behavior. There is minor redundancy between 'for release planning and tracking' and the Fix Version sentence, but nothing that wastes real space.

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 six-parameter mutation with no annotations and no output schema, the definition should say what comes back (e.g., the created version ID/key) and what permissions or validation rules apply. Those omissions leave the agent without enough to predict the result or recover from errors, though the core action is clear.

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%, so the schema already documents all six parameters including date formats and examples, making 3 the baseline. The description adds marginal meaning by explaining the intent of the released flag and the Fix Version relationship, but adds nothing about date interactions (e.g., releaseDate vs startDate) beyond the schema.

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: 'Create a new version/release in a Jira project,' which is distinct from sibling operations like jira_create_sprint or jira_create_issue. It also clarifies the domain role of a version ('used as Fix Version values on issues'), but never explicitly contrasts itself with the nearest sibling, so it falls short of a 5.

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

Usage Guidelines2/5

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

The phrase 'for release planning and tracking' hints at intent but gives no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. There is also no mention of prerequisites such as project admin permission or name-uniqueness constraints, leaving the agent to infer call conditions.

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