Skip to main content
Glama
its-qusai-nasr

Jira Admin MCP Server

jira_projects_create_version

Create a new version or release in a Jira project by specifying project key, version name, optional release date, and release status.

Instructions

Create a new version (release) in a project.

Returns: {id, name, project_key}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_keyYesProject key
nameYesVersion name, e.g. 'v1.0', '2026-Q1'
descriptionNoVersion description
release_dateNoRelease date in YYYY-MM-DD format
releasedNoMark as released. Default: False

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations indicate readOnlyHint=false, which aligns with the creation purpose. The description adds no additional behavioral context beyond stating it creates a version. With annotations covering the write nature, a score of 3 is appropriate as no extra traits are revealed.

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 extremely concise with two sentences: one for purpose and one for return structure. No wasted words, and the key information is front-loaded.

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 simplicity of the tool (create a version with optional fields), the description combined with the rich schema and annotations covers the essential aspects. The return shape is specified. It could mention potential errors or permissions, but overall it is sufficiently complete.

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 all parameters have descriptions in the input schema. The description only mentions return values, adding no new meaning beyond what the schema provides. Baseline 3 is correct.

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 clearly states the verb 'Create' and the resource 'a new version (release) in a project.' It is specific and distinguishable from sibling tools like jira_projects_get_versions or jira_projects_list.

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 guidance on when to use this tool versus alternatives. Among siblings, there are tools for listing versions (jira_projects_get_versions) and other project operations, but the description does not provide any context for selection or exclusion.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/its-qusai-nasr/jira-admin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server