Skip to main content
Glama
vish288

mcp-atlassian-extended

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Jira Update Version

jira_update_version
Idempotent

Modify an existing Jira version to rename it, adjust dates, description, or set archived/released status. Works with Jira Server, Data Center, and Cloud.

Instructions

Update an existing Jira version (REST API v2, supports Server/DC and Cloud).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew version name
archivedNoMark as archived
releasedNoMark as released
start_dateNoStart date (YYYY-MM-DD)
version_idYesNumeric version ID
descriptionNoNew description
release_dateNoRelease date (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.15.1
    • changedInput schema / properties / version_id / description
      Previous value: -"Version ID"New value: +"Numeric version ID"
    • removedInput schema / properties / version_id / minLength
      Removed value: -1
    • addedInput schema / properties / version_id / pattern
      Added value: +"^\\d+$"
    • 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, idempotentHint=true and openWorldHint=true, so the safety and repeat-call profile is covered. The description adds platform/deployment context (REST API v2, Server/DC and Cloud) but says nothing about partial-update semantics, permissions required, or what happens to omitted fields.

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 verb, resource and environment support are all packed into one clause with zero waste.

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 7-parameter mutation tool with no output schema, the description covers the bare essentials and annotations carry the safety profile. However it omits partial-update behavior and any hint about the returned version object, leaving meaningful gaps.

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%, so every parameter including version_id, name, archived, released and the date fields is already documented in the schema. The description adds no format or semantic detail beyond that, so the 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 (Update) and resource (Jira version), which is unambiguous and clearly distinct from jira_create_version and jira_get_project_versions. It does not explicitly contrast itself with any sibling, so it stops 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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as jira_create_version or jira_get_project_versions. The agent is left to infer that this applies only to versions that already exist.

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