Polarion MCP Server

patchTestStepResultAttachment

Idempotent

Rename or replace the file of an existing test step result attachment without changing its attachment ID.

Instructions

Updates one existing Test Step Result attachment: its metadata (e.g. title) via requestBody.resource, and optionally replaces the stored file by passing base64-encoded bytes in requestBody.content. The attachment keeps its ID. Use this to rename or re-upload a file that already exists; to add a new file use postTestStepResultAttachments, and to read the current file use getTestStepResultAttachmentContent. 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
`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.
`iteration`	Yes	The iteration number identifying which repeated occurrence of this item is being addressed (e.g. which run of a test parameter).
`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.
`testRunId`	Yes	The Test Run's ID within its project.
`testCaseId`	Yes	The Test Case's ID being referenced.
`requestBody`	No	Attachment metadata and file data.
`attachmentId`	Yes	The attachment's ID, as returned by the corresponding list- or get-attachments call for this resource.
`testStepIndex`	Yes	The Test Step index.
`testCaseProjectId`	Yes	The project ID that owns the referenced Test Case — may differ from the project in the request path when the test case is shared from another project.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv1.2.0Sep 17, 2026

changedInput schema / properties / attachmentId / description

Previous value: -"The Attachment ID."New value: +"The attachment's ID, as returned by the corresponding list- or get-attachments call for this resource."

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 / iteration / description

Previous value: -"The Iteration Number."New value: +"The iteration number identifying which repeated occurrence of this item is being addressed (e.g. which run of a test parameter)."

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 / testCaseId / description

Previous value: -"The Testcase ID."New value: +"The Test Case's ID being referenced."

changedInput schema / properties / testCaseProjectId / description

Previous value: -"The Testcase Project ID."New value: +"The project ID that owns the referenced Test Case — may differ from the project in the request path when the test case is shared from another project."

changedInput schema / properties / testRunId / description

Previous value: -"The Test Run ID."New value: +"The Test Run's ID within its project."

Changed2 schema fields 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"
+}

changedInput schema / properties / requestBody / description

Previous value: -"Attachment meta data and file data."New value: +"Attachment metadata and file data."

First observedv1.0.0Jun 13, 2026

TDQS

A4.6/5.0

Behavior4/5

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

The description discloses idempotent behavior, aligning with the idempotentHint annotation, and adds the dry_run behavior including the note about error-flagged preview results. It explains that the attachment keeps its ID and the effect of repeated calls, adding value beyond 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 longer than average but well-structured, front-loading the main purpose and then providing usage guidance, idempotency, and dry_run behavior. Each sentence adds value without unnecessary fluff.

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 9 parameters and no output schema, the description covers all necessary aspects: what it does, when to use it, the effect of dry_run, idempotency, and the differentiation from siblings. An agent has enough information to invoke it correctly.

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%, but the description adds meaning by explaining that requestBody.resource holds metadata and requestBody.content holds base64 bytes, which the schema merely labels as 'Attachment metadata and file data'. The dry_run parameter's behavior is also detailed in the description, beyond the schema's description.

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 an existing Test Step Result attachment, specifying it can rename metadata via requestBody.resource and re-upload content via requestBody.content. It explicitly distinguishes itself from siblings by naming postTestStepResultAttachments for adding and getTestStepResultAttachmentContent for reading.

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 says 'Use this to rename or re-upload a file that already exists' and names the alternatives for adding and reading. The dry_run tip also provides a concrete usage pattern for previewing requests, making it clear when to use this tool.

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

Deploy Server

patchTestStepResultAttachment

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools