Skip to main content
Glama
vish288

mcp-atlassian-extended

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Jira Create Version

jira_create_version

Create a new version in a Jira project with a name, optional release details, dates, and status. Use it to define and manage project versions for planning releases.

Instructions

Create a new version in a Jira project (REST API v2, supports Server/DC and Cloud).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesVersion name
archivedNoMark as archived
releasedNoMark as released
start_dateNoStart date (YYYY-MM-DD)
descriptionNoVersion description
project_keyYesProject key (e.g. PROJ)
release_dateNoRelease date (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.1
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. First observedv0.6.13

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the write/non-deterministic nature is covered. The description adds deployment-scope context (REST API v2, Server/DC and Cloud support) beyond the annotations, but says nothing about permission requirements or the uniqueness/duplicate-name error case that a version-creation call commonly hits.

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 the action first and the compatibility note trailing in parentheses; there is no filler or redundancy.

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?

With a fully documented 7-parameter schema and no output schema, the description need not explain return values, so the structured fields carry most of the load. However, for a mutation tool it omits the practical context an agent needs (auth/permission expectations, duplicate-name failure mode), leaving it merely adequate.

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% with all 7 parameters (name, project_key, archived, released, start_date, release_date, description) documented inline, including date formats and defaults. The description adds no parameter semantics beyond the schema, so baseline 3 applies.

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 and resource ('Create a new version in a Jira project'), so the agent knows exactly what the tool produces. It does not distinguish itself from the sibling jira_update_version or jira_get_project_versions, relying on the verb alone to separate them.

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 description offers no when-to-use guidance, no prerequisites (e.g. project admin permission needed to create versions), and no routing to alternatives such as jira_update_version or jira_get_project_versions. The parenthetical about REST API v2 is compatibility context, not usage guidance.

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

Deploy Server

Other Tools