Polarion MCP Server

postTestStepResults

Records execution results for Test Steps in a Polarion Test Run, capturing outcomes and comments per iteration. Run with dry_run first to validate arguments and preview the request.

Instructions

Creates execution results for Test Steps in a Test Record. Use getTestSteps for the Test Case definition and getTestStepResults to read recorded outcomes. Effect: creates a new resource. Repeating this call may create additional resources; it is not guaranteed idempotent. Tip: set dry_run: true first to validate the arguments and preview the exact request without sending it to Polarion. The executor returns this preview as normal text, and as structured content when the tool declares an output schema.

Input 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. If the ID is unknown, ask the user; getProjects lists IDs only with global read access.
`testRunId`	Yes	The Test Run's ID within its project.
`testCaseId`	Yes	The Test Case's ID being referenced.
`requestBody`	Yes	The Test Step Result(s) body.
`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.

Output Schema

Name	Required	Description	Default
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.4.4Oct 29, 2026

changedInput schema / properties / projectId / description

Previous 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."New value: +"The Polarion project ID (its URL segment, e.g. `myproject`), case-sensitive. Required to scope the request to one project. If the ID is unknown, ask the user; getProjects lists IDs only with global read access."

Changed9 schema fields changedv1.3.1Oct 22, 2026

removedOutput schema / properties / data / items / properties / id / example
```
Removed value: -"MyProjectId/MyTestRunId/MyProjectId/MyTestcaseId/0/1"
```

changedOutput schema / properties / data / items / properties / id / type

Previous value: -"string"New value: +[
+  "string",
+  "number",
+  "integer",
+  "boolean",
+  "null"
+]

removedOutput schema / properties / data / items / properties / links / properties / self / example

Removed value: -"server-host-name/application-path/projects/MyProjectId/testruns/MyTestRunId/testrecords/MyProjectId/MyTestcaseId/0/teststepresults/1"

changedOutput schema / properties / data / items / properties / links / properties / self / type

Previous value: -"string"New value: +[
+  "string",
+  "number",
+  "integer",
+  "boolean",
+  "null"
+]

changedOutput schema / properties / data / items / properties / links / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
removedOutput schema / properties / data / items / properties / type / enum
```
Removed value: -[
-  "teststep_results"
-]
```

changedOutput schema / properties / data / items / properties / type / type

Previous value: -"string"New value: +[
+  "string",
+  "number",
+  "integer",
+  "boolean",
+  "null"
+]

changedOutput schema / properties / data / items / type

Previous value: -"object"New value: +[
+  "object",
+  "null"
+]

changedOutput schema / properties / data / type

Previous value: -"array"New value: +[
+  "array",
+  "null"
+]

Changed6 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 / 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."

Changed1 schema field changedv1.1.0Sep 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "items": {
+        "properties": {
+          "id": {
+            "example": "MyProjectId/MyTestRunId/MyProjectId/MyTestcaseId/0/1",
+            "type": "string"
+          },
+          "links": {
+            "properties": {
+              "self": {
+                "example": "server-host-name/application-path/projects/MyProjectId/testruns/MyTestRunId/testrecords/MyProjectId/MyTestcaseId/0/teststepresults/1",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": {
+            "enum": [
+              "teststep_results"
+            ],
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

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

A3.6/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the description's 'creates a new resource' and 'not guaranteed idempotent' largely echo structured data. The genuinely additive parts are the dry_run preview tip and the note about how the preview is returned as text and structured content.

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 purpose and the write-effect warning are front-loaded, and no sentence is filler. The closing sentence about executor preview mechanics is slightly more verbose than needed for a description that already has a schema-documented dry_run.

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?

With an output schema present and full parameter documentation, the description covers what an agent needs: what it creates, what it is not for, that it is non-idempotent, and that dry_run is available. Remaining gaps (permissions, error behavior) are minor given the annotation and schema richness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all seven parameters, including the nested requestBody shape, are already documented. The description only touches dry_run, which the schema also explains thoroughly, so it adds little parameter meaning beyond the structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a specific verb and resource ('Creates execution results for Test Steps in a Test Record'), which is far more than a restatement of the name. It also routes reads to getTestSteps and getTestStepResults, though it does not differentiate itself from bulk-ingest siblings such as importXUnitTestResults or postTestSteps.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly names the read-side alternatives (getTestSteps for the definition, getTestStepResults for recorded outcomes), which tells an agent when not to use this tool. It stops short of stating preconditions or when bulk import is preferable over this per-step writer.

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

Deploy Server