Skip to main content
Glama

update_work_items

DestructiveIdempotent

Update up to 50 work items atomically by patching specified fields; list fields like assignees and hyperlinks are fully replaced.

Instructions

Update fields on 1-50 existing work items in one bulk PATCH; unset fields stay unchanged. 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. Atomic: one bad item rejects the whole batch.

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. To add a table, caption, image, link, or widget, call get_html_recipes first and adapt its template before writing description_html — hand-written table markup is rejected. workitemimg:{id} image refs must name an existing attachment — confirm via list_work_item_attachments first.

custom_fields is partial; keys outside the type schema are rejected, values are not validated — resolve via list_work_item_enum_options first. module is not settable here — use move_work_item_to_document / move_work_item_from_document. workflow_action/change_type_to apply to EVERY item; change_type_to rescopes enums to the target type and resets status. 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?

Beyond annotations (destructiveHint=true, idempotentHint=true), the description details specific behaviors: list replacement, atomic batch failure, verbatim description_html handling, and status reset on type change. It fully discloses side effects and requirements.

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 fairly long but every sentence is necessary due to the tool's complexity. It is well-structured with clear warnings and action steps. Slight reduction could be possible, but overall it is efficient for the information density.

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 covers all needed context: batch size limit, atomicity, list replacement semantics, description_html constraints, custom_fields behavior, and return value. It also references sibling tools where appropriate. No gaps remain.

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?

With 100% schema coverage, the description adds significant value by explaining how to use each parameter correctly, e.g., highlighting that hyperlinks and assignee_ids replace lists, that description_html must come from get_work_item or get_html_recipes, and that custom_fields values are not validated. This goes well beyond the schema alone.

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 tool updates existing work items in bulk (1–50), using a PATCH-like semantic. It explicitly distinguishes itself from sibling tools like create_work_items (create) and move_work_item_from_document (module change).

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 extensive guidance on when to use this tool, including warnings about replacing lists (hyperlinks, assignee_ids), the need to read items first, and alternatives for module changes (move_work_item_*). It also covers constraints like atomicity and the requirement to use get_html_recipes for rich descriptions.

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