Skip to main content
Glama
TarasKhust

@tarasrushchak/jira-mcp-server

by TarasKhust

update_ticket_fields

Update any field of a Jira ticket including estimate, story points, labels, assignee, priority, due date, and custom fields.

Instructions

Update fields of a Jira ticket (e.g., original estimate, story points, labels, assignee, priority, due date, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticketIdYesThe Jira ticket ID (e.g., PROJECT-123)
originalEstimateNoOriginal estimate in Jira time format (e.g., '1d', '2h', '1w 2d 3h', '30m')
remainingEstimateNoRemaining estimate in Jira time format
storyPointsNoStory points (numeric value)
labelsNoArray of labels to set
summaryNoTicket summary
descriptionNoTicket description
assigneeNoAssignee email, accountId, or username. Use 'null' to unassign
reporterNoReporter email, accountId, or username
priorityNoPriority name (e.g., 'Urgent', 'High', 'Medium', 'Normal', 'Low', 'Lowest', 'Unprioritized')
dueDateNoDue date in ISO format (YYYY-MM-DD) or 'null' to remove
customFieldsNoCustom fields as key-value pairs where key is field ID (e.g., 'customfield_10000': 'value')
Behavior2/5

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

Annotations are absent, so the description must fully convey behavioral traits. It only states 'Update fields' without disclosing mutation behavior, required permissions, reversibility, or whether partial updates are supported.

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?

Single sentence, efficient and front-loaded with verb and resource. No wordiness, but could be structured more to separate purpose from examples.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 12 parameters, no output schema, no annotations, and sibling tools that update specific fields, the description lacks completeness. It does not clarify partial updates, overlapping with other tools, or response behavior.

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 parameter detail is already provided. The description adds minimal extra meaning (just lists example fields). Baseline of 3 is appropriate.

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 'Update' and the resource 'fields of a Jira ticket', with specific examples (original estimate, story points, etc.). This distinguishes it from sibling tools like assign_ticket or update_status.

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 vs alternatives (e.g., assign_ticket, update_status). The description does not mention when it should or should not be used.

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/TarasKhust/jira-mcp-server'

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