Skip to main content
Glama

Update Form Answers

jira_update_proforma_form_answers
Destructive

Update answers in Jira ProForma forms for an issue. Provide question IDs, answer types, and values to modify form responses via the Jira Forms REST API.

Instructions

Update form field answers using the Jira Forms REST API.

This is the primary method for updating form data. Each answer object must specify the question ID, answer type, and value.

⚠️ KNOWN LIMITATION - DATETIME fields: The Jira Forms API does NOT properly preserve time components in DATETIME fields. Only the date portion is stored; times are reset to midnight (00:00:00).

Workaround for DATETIME fields: Use jira_update_issue to directly update the underlying custom fields instead:

  1. Get the custom field ID from the form details (question's "jiraField" property)

  2. Use jira_update_issue with fields like: {"customfield_XXXXX": "2026-01-09T11:50:00-08:00"}

Example:

# Instead of updating via form (loses time):
# jira_update_proforma_form_answers(issue_key, form_id, [{"questionId": "91", "type": "DATETIME", "value": "..."}])

# Use direct field update (preserves time):
jira_update_issue(issue_key, {"customfield_10542": "2026-01-09T11:50:00-08:00"})

Automatic DateTime Conversion: For DATE and DATETIME fields, you can provide values as:

  • ISO 8601 strings (e.g., "2024-12-17T19:00:00Z", "2024-12-17")

  • Unix timestamps in milliseconds (e.g., 1734465600000)

The tool automatically converts ISO 8601 strings to Unix timestamps.

Example answers: [ {"questionId": "q1", "type": "TEXT", "value": "Updated description"}, {"questionId": "q2", "type": "SELECT", "value": "Product A"}, {"questionId": "q3", "type": "NUMBER", "value": 42}, {"questionId": "q4", "type": "DATE", "value": "2024-12-17"} ]

Common answer types:

  • TEXT: String values

  • NUMBER: Numeric values

  • DATE: Date values (ISO 8601 string or Unix timestamp in ms)

  • DATETIME: DateTime values - ⚠️ USE WORKAROUND ABOVE

  • SELECT: Single selection from options

  • MULTI_SELECT: Multiple selections (value as list)

  • CHECKBOX: Boolean values

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
answersYesList of answer objects. Each answer must have: questionId (string), type (TEXT/NUMBER/SELECT/etc), value (any)
form_idYesProForma form UUID (e.g., '1946b8b7-8f03-4dc0-ac2d-5fac0d960c6a')
issue_keyYesJira issue key (e.g., 'PROJ-123')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond the destructiveHint=true annotation, the description discloses a critical behavioral limitation: the Jira Forms API does not preserve time components in DATETIME fields. It also explains automatic conversion of ISO 8601 dates to Unix timestamps, and provides example answer structures. This adds significant behavioral context that an agent needs to know before calling the tool.

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?

The description is long but well-organized with clear sections: purpose, known limitation, workaround, automatic conversion, examples, and type list. Each section serves a purpose, though the workaround example repeats the limitation slightly. It could be slightly trimmed, but the length is justified given the tool's complexity and important caveats.

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

Completeness5/5

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

The description is exceptionally complete. It covers the tool's purpose, the answers array format, common answer types, date/time conversion rules, a known limitation, and a workaround referencing a sibling tool. The output schema exists, so return values need not be explained. Given the tool's complexity and the importance of the DATETIME caveat, this description leaves no critical gaps.

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

Parameters5/5

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

Although the schema provides 100% coverage with basic descriptions, the description vastly enriches parameter semantics. It explains the structure of the 'answers' array with a detailed example, lists common answer types (TEXT, NUMBER, SELECT, etc.) and their expected value formats, and clarifies special date/datetime handling. This goes far beyond the schema's generic 'additionalProperties' schema.

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 begins with a specific verb and resource: 'Update form field answers using the Jira Forms REST API.' It explicitly identifies this as 'the primary method for updating form data,' distinguishing it from sibling tools like jira_update_issue and jira_get_proforma_form_details. The purpose is unambiguous and well-scoped.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidance by stating this is the primary method for updating form data and gives a concrete when-not-to-use scenario: for DATETIME fields, it instructs to use jira_update_issue instead, with a detailed workaround. This distinguishes usage from alternatives and provides clear contextual instructions.

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/hieptran87/atlassian-mcp-server'

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