Skip to main content
Glama

update_work_items

DestructiveIdempotent

Update fields on multiple work items in one bulk PATCH. Pass full hyperlink and assignee lists to avoid data loss, and optionally apply workflow transitions or change work item type.

Instructions

Update fields on 1-50 existing work items in one bulk PATCH; unset fields stay unchanged. Per-item hyperlinks/assignee_ids REPLACE the stored lists: even to add ONE entry, call get_work_item on the target BEFORE updating and resubmit every existing entry plus the new one — anything omitted is silently deleted.

description_html is raw Polarion HTML, sent verbatim — source from get_work_item(include_description_html=True); greenfield bodies use create_work_items Markdown, formats never mix. New table, caption, link, or widget HTML must be adapted from get_html_recipes templates, never hand-written. custom_fields is partial, keys outside the type schema rejected, values NOT validated — resolve via list_work_item_enum_options first.

module not settable here — use move_work_item_to_document / move_work_item_from_document. workflow_action/change_type_to apply to EVERY item; each item needs ≥1 body field (else 400); change_type_to scopes status/severity/resolution to the target type and resets status. Unknown enum ids and missing/duplicate work_item_ids raise ValueError. Atomic: one bad item rejects the whole batch. Returns ids only — re-read via get_work_item if needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesPer-item changes (1-50). hyperlinks/assignee_ids REPLACE the stored lists — read each item first and pass full lists, not deltas.
dry_runNoPreview payload without writing; guards still query Polarion.
project_idYesPolarion project ID.
change_type_toNoNew work-item type for EVERY item; RESETS status.
workflow_actionNoWorkflow action ID (e.g. 'close'); applies to EVERY item.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runYes
updatedYes
work_item_idsNo
payload_previewNo
Behavior5/5

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

Adds extensive behavioral context beyond annotations: hyperlinks/assignee_ids replace lists, description_html is raw HTML, custom_fields validation, atomic batch, return only ids, workflow_action applies to all items. No contradiction with annotations.

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 comprehensive and well-structured, with the main action first followed by detailed caveats. Every sentence adds necessary information; no fluff. Could be slightly more structured with bullet points, but still efficient.

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 the tool's complexity, schema coverage, and annotations, the description covers all essential aspects: scope, prerequisites, error handling, atomicity, return format. References related tools for further steps (get_work_item, move_work_item_*). Complete.

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 100%, so baseline is 3. Description adds valuable usage nuances like hyperlinks replacement semantics, HTML sourcing rules, custom_fields resolution, and workflow_action scope. That extra context earns a 4.

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 it updates fields on 1-50 existing work items in a bulk PATCH. It distinguishes from sibling tools like create_work_items and delete_work_item_links by specifying it updates existing 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 when-to-use (bulk update), when-not-to (module changes require move_work_item_to_document), and alternatives (get_work_item before updating, use create_work_items for greenfield, list_work_item_enum_options for custom fields). Covers error conditions and best practices.

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