Polarion MCP Server

patchWorkItemApproval

Idempotent

Update the approval status of a single work item in Polarion by specifying project, work item ID, user ID, and the desired status. Preview changes with dry_run before applying.

Instructions

Updates the specified instance. Cardinality: targets a single item by ID. For the full collection or a batch, use patchWorkItemApprovals instead. Effect: idempotent — calling it again with the same input leaves the resource in the same end state, with no additional side effects. Tip: set dry_run: true first to preview the exact request Polarion would receive, without changing anything. On tools with a typed output schema, this preview is returned as an error-flagged result since it is not real tool output -- read the text content regardless of that flag.

Input Schema

TableJSON Schema

Name	Required	Description
`userId`	Yes	The User ID.
`dry_run`	No	If true, validates the request and returns the exact request that would be sent to Polarion — with the Authorization header redacted and any binary payload summarized by byte length — without actually sending it.
`projectId`	Yes	The Polarion project ID (its URL segment, e.g. `myproject`), case-sensitive. Required to scope the request to one project; call getProjects to list valid IDs.
`workItemId`	Yes	The Work Item's ID within its project (e.g. `WI-123`), not the combined `project/id` path used in some link payloads.
`requestBody`	Yes	The Test Run(s) body.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.2.0Sep 17, 2026

changedInput schema / properties / dry_run / description

Previous value: -"If true, validate and return the request that would be sent without calling Polarion."New value: +"If true, validates the request and returns the exact request that would be sent to Polarion — with the Authorization header redacted and any binary payload summarized by byte length — without actually sending it."

changedInput schema / properties / projectId / description

Previous value: -"The Project ID."New value: +"The Polarion project ID (its URL segment, e.g. `myproject`), case-sensitive. Required to scope the request to one project; call getProjects to list valid IDs."

changedInput schema / properties / workItemId / description

Previous value: -"The Work Item ID."New value: +"The Work Item's ID within its project (e.g. `WI-123`), not the combined `project/id` path used in some link payloads."

Changed1 schema field changedSep 7, 2026

addedInput schema / properties / dry_run

Added value: +{
+  "description": "If true, validate and return the request that would be sent without calling Polarion.",
+  "type": "boolean"
+}

First observedv1.0.0Jun 13, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the idempotentHint annotation, the description explicitly explains what idempotency means in this context (same end state, no extra side effects) and details the dry_run behavior, including how preview results are returned with an error flag and how to interpret them. This adds meaningful behavioral context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact, with only two sentences covering purpose, differentiation, idempotency, and dry_run guidance. It is front-loaded with the primary action and efficiently packs high-value information without redundancy.

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

Completeness4/5

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

The description covers the essential operational aspects: single-target scope, batch alternative, idempotency, and dry_run preview. Since there is no output schema, the description doesn't need to detail return values, but it doesn't explicitly mention expected success/failure responses beyond the preview. However, given the simplicity of the operation and the strong schema annotations, this is mostly 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?

The input schema already provides detailed descriptions for all parameters, including examples and clarification on `workItemId` versus combined path. The description adds a useful tip about `dry_run` and clarifies the preview mechanism, supplementing the schema with practical usage intent.

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 a single specified instance, identifies the exact resource it targets, and calls out the sibling tool `patchWorkItemApprovals` for batch operations, making its purpose and distinction unambiguous.

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?

It explicitly advises using `patchWorkItemApprovals` for collections or batches, provides a concrete tip to use `dry_run` for previewing requests, and explains the preview behavior, which gives clear guidance on when and how to use this tool versus alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

patchWorkItemApproval

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools