Polarion MCP Server

postOslcResources

Add OSLC links from a Polarion Work Item to external artifacts in other OSLC-capable tools. Enables cross-tool traceability for related change requests and other linked resources.

Instructions

Adds one or more OSLC links from a Work Item to artifacts in other OSLC-capable tools: each requestBody.data entry gives the remote artifact's uri, an OSLC link role URI (e.g. http://open-services.net/ns/cm#relatedChangeRequest), and an optional label. Use it for cross-tool traceability; to link Polarion Work Items to each other use postLinkedWorkItems, and to list existing OSLC links use getOslcResources. Effect: creates a new resource on each call — calling it again with the same input creates a duplicate; it is not idempotent. 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.
`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 Linked Oslc Item(s) body.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No

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 changedv1.1.0Sep 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "items": {
+        "properties": {
+          "id": {
+            "example": "MyProjectId/MyWorkItemId/http://server-host-name/ns/cm#relatedChangeRequest/http://server-host-name/application-path/oslc/services/projects/MyProjectId/workitems/MyWorkItemId",
+            "type": "string"
+          },
+          "links": {
+            "type": "object"
+          },
+          "type": {
+            "enum": [
+              "linkedoslcresources"
+            ],
+            "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

A4.9/5.0

Behavior5/5

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

Discloses the key behavioral consequence beyond annotations: the call creates a new resource and is not idempotent, so repeating input produces duplicates. It also explains the dry_run preview behavior, including the unusual error-flagged result on typed output schemas.

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?

Every sentence earns its place: function, field semantics, alternative routing, non-idempotence warning, and dry_run tip. The most actionable information is front-loaded before the dry_run caveat.

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?

For a tool with nested requestBody, output schema, and multiple related siblings, the description covers function, usage vs alternatives, side effects, and preview semantics. Nothing needed to decide when and how to call it is left out.

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?

Top-level schema descriptions already cover projectId, workItemId, and requestBody, so baseline is 3. The description adds value by explaining the meaning of the nested uri, role, and label fields and gives a concrete role URI example, which the schema leaves bare.

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?

States a specific action ('Adds one or more OSLC links from a Work Item to artifacts in other OSLC-capable tools') and enumerates the requestBody fields. It also differentiates from siblings by explicitly naming postLinkedWorkItems for internal links and getOslcResources for listing.

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 selection criteria: use for cross-tool traceability, use postLinkedWorkItems for internal Work Item links, and use getOslcResources to list existing links. It also recommends dry_run for preview before committing.

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

Deploy Server