Skip to main content
Glama

update_work_item

DestructiveIdempotent

Update an existing Polarion work item by modifying fields like title, status, hyperlinks, assignees, or custom fields. Supports workflow actions, type changes, and dry-run validation.

Instructions

Update an existing Polarion work item.

PATCHes supplied fields, then GETs so current reflects the change. None / empty all mean leave unchanged — no clear path.

description_html is RAW Polarion HTML, verbatim, no sanitization (NEVER pass untrusted input); round-trip with get_work_item(include_description_html=True). Greenfield: use create_work_items Markdown — paths never mix.

hyperlinks / assignee_ids REPLACE (full list, not delta); each hyperlink role validated against hyperlink-role (before PATCH, on dry_run too). custom_fields partial; a key absent from the type's sampled schema is rejected (a type with no populated customs blocks it).

module NOT exposed — use move_work_item_to_document / move_work_item_from_document. Prefer workflow_action over raw status; workflow_action / change_type_to MUST pair with ≥1 body field (empty PATCH 400s). Unknown status / severity / resolution / priority / change_type_to raise ValueError listing valid options; with change_type_to set, status/severity/resolution scope to the target type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesPolarion project ID.
work_item_idYesShort ID of an EXISTING work item (e.g. 'MCPT-042').
titleNo
description_htmlNoNew raw Polarion HTML body (round-trip shape from get_work_item).
statusNoNew workflow status; prefer ``workflow_action`` for real transitions.
priorityNoNew priority string (e.g. '50.0').
severityNo
due_dateNoNew due date 'YYYY-MM-DD'.
initial_estimateNoNew Polarion duration (e.g. '5 1/2d', '1w 2d').
resolutionNoNew resolution outcome; prefer ``workflow_action`` so workflow rules apply.
hyperlinksNoREPLACES the hyperlink list — pass the full list, not a delta.
assignee_idsNoREPLACES the assignee list — pass the full list, not a delta.
custom_fieldsNoPartial custom-field update; rich-text values must be ``{'type':'text/html','value':...}``.
workflow_actionNoWorkflow action ID (e.g. 'close'); must be paired with at least one body field.
change_type_toNoChange work-item type; RESETS status; must be paired with at least one body field.
include_current_description_htmlNoWhen True, return the post-PATCH raw HTML body in ``current.description_html``.
dry_runNoWhen True, return the payload preview without writing; enum/custom-field guards still query Polarion, so the work item must be readable and the validation endpoint reachable.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
updatedYes
dry_runYes
currentYes
changesYes
payload_previewYes
Behavior5/5

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

Adds significant behavioral details beyond annotations: PATCH then GET, 'description_html' is raw HTML without sanitization, 'hyperlinks'/'assignee_ids' replace lists, 'custom_fields' partial update, validation occurs on dry_run. No contradictions with annotations (destructiveHint=true, idempotentHint=true).

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?

Well-structured with a clear first sentence and bullet-point style for key behaviors. Some repetition (e.g., 'None/empty all mean leave unchanged' could be more concise), but every sentence is informative and front-loaded.

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?

Given 17 parameters and complex behaviors (replacement vs delta, HTML security, workflow actions), the description covers critical context including alternatives, error handling, and parameter constraints. Output schema exists, so return values are not essential.

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 coverage is high (88%), but description adds practical context for many parameters: 'description_html' round-trip, 'hyperlinks' replacement, 'workflow_action' pairing, 'dry_run' validation behavior. Some parameters like 'title' lack added semantics, but overall adds value beyond 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?

Description explicitly states 'Update an existing Polarion work item' with specific verb and resource. It distinguishes from siblings like 'move_work_item_to_document' and 'create_work_items' by noting that 'module NOT exposed' and greenfield use Markdown from 'create_work_items'.

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?

Provides explicit guidance: prefer 'workflow_action' over raw 'status', 'workflow_action'/'change_type_to' must pair with a body field, and unknown values raise ValueError with valid options. Also explains when to use 'move_work_item_to_document' for module.

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/devemberx/mcp-server-polarion'

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