Skip to main content
Glama
Sign In
atlassian-browser-mcp

atlassian-browser-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Update Version

jira_update_version
Destructive

Update an existing Jira fix version by changing only supplied fields: rename it, shift release dates, edit description, or set archived/released status without recreating it.

Instructions

Update an existing fix version in a Jira project.

Only fields explicitly provided are modified; other attributes of the version are left untouched. Useful for archiving/unarchiving versions, renaming, or shifting release dates without recreating them.

Input Schema

NameRequiredDescriptionDefault
nameNoNew name for the version
archivedNoSet archived flag (true to archive)
releasedNoSet released flag (true to mark released)
start_dateNoNew start date (YYYY-MM-DD)
version_idYesNumeric ID of the version to update (e.g. '10001')
descriptionNoNew description for the version
release_dateNoNew release date (YYYY-MM-DD)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.1
    • addedInput schema / additionalProperties
      Added value: +false
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  2. Addedv1.2.1

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false. The description adds a valuable partial-update behavior: only explicitly provided fields are modified and other attributes remain untouched, which is important context beyond the annotations.

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?

The description is three tight sentences with no wasted wording. The purpose and partial-update behavior are front-loaded, followed by concrete use cases.

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?

Given the rich schema, output schema, and annotations, the description covers the essential update behavior and use cases. It could say more about permissions or side effects of archiving/releasing, but the annotations already flag destructive and open-world behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the parameter schema already explains each field. The description adds meaningful semantics beyond the schema by clarifying that omitted fields are left unchanged, which helps an agent understand optional parameter behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: update an existing fix version in a Jira project. It clearly distinguishes this from creation tools such as jira_create_version by emphasizing an existing version and avoiding recreation.

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: archiving/unarchiving, renaming, and shifting release dates without recreating the version. It implies this is the tool for modifying an existing version, though it does not explicitly name alternatives or exclusions.

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