Polarion Mcp

io.github.phillipboesgerPublished by GitHub account phillipboesgerv1.5.0Updated Nov 4, 2026

Polarion ALM MCP server for requirements, LiveDocs, work items, traceability and test management.

Overview

AI-generated overview

Connects an assistant to a Polarion ALM instance over its REST API to search requirements, read LiveDocs, manage work items, plans and test runs.

What you can do
  • Search and read work items, including cross-project queries and traceability links
  • Read LiveDocs, document parts, pages and attachments
  • Create, update and delete work items, approvals, links and custom fields
  • Prepare test runs and record test results, parameters and attachments
  • Manage projects, plans, collections, enumerations and license slots
  • Preview any write with dry_run before it is sent
When to use it
Useful when a team keeps requirements, defects, documents and test management in Polarion and wants an assistant to triage, draft updates or summarize release scope without leaving the chat. Read-only use is possible for pure lookup and review work.
Requirements
A local process started with npx (Node.js 22+ and npm/npx) or the Docker image; a REST-enabled Polarion instance. Requires API_BASE_URL and a personal access token supplied as BEARER_TOKEN. Calls run with the token owner's permissions.
Before you install
The token grants the assistant the owner's Polarion permissions, including writes and irreversible deletes of work items, projects, plans and test data. Set MCP_READ_ONLY=1 to expose read tools only, and preview writes with dry_run. Tool results are sent to your AI provider, so your organization's data policies apply; keep the token out of version control.

Installation

In SourceWeft

  1. Open Polarion Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Polarion MCP

Your Polarion work, one conversation away.

Find requirements, review documents and prepare test runs through your AI assistant. An open-source Model Context Protocol server that exposes every Polarion REST operation (284 tools, generated from the current API definition).

[CI] [npm version] [Docker image] [License: MIT]

Connect your assistant · Daily workflows · Tool catalog

[Polarion MCP works with Claude, ChatGPT, Gemini, VS Code, Copilot, Cursor and Codex.]

On this page:

What the connector does for you

[Your AI client sends tool calls to Polarion MCP, which turns them into REST requests against your Polarion]

Your AI client → Polarion MCP → your Polarion REST API. Ask a question; the assistant chooses tools, reads the returned data and proposes an answer or change.

  • Find answers: search requirements and defects, read LiveDocs and inspect traceability links.
  • Prepare work: draft test cases, prepare runs and record the test outcomes your team supplies.
  • Change data, safely: the assistant can create and update Polarion data, and every write can be previewed first (dry_run: true shows the exact request without sending it). Prefer read access only? MCP_READ_ONLY=1 blocks all writes. Set approval rules in your AI client; previews do not create an approval lock.
  • Inspect what you run: MIT source, build provenance and signed container images. See supply-chain verification.

[Topic cards: work items, test management, plans, documents and more, covering every Polarion REST operation]

DomainOutcome
Work itemsFind requirements, triage defects, prepare field updates.
Documents and pagesRead LiveDocs, inspect parts, manage attachments and supported pages.
Test managementPrepare runs and record supplied results.
Plans and collectionsReview release scope and document collections.
Projects, people and configurationDiscover accessible projects, users, allowed field values and metadata.

The landing page shows counts by domain, computed from src/tools.ts. The 284 tools count covers generated REST operations; configured toolsets and additional helpers change the exposed catalog. Selected Work Item writes validate enumeration values, custom-field keys and user references. Features and limits describe the scope.

A day with Polarion MCP

[Five example conversations: release triage, document review, test preparation, release status and traceability gaps]

These are illustrative conversations using real tools, not recorded outputs. Project types, link roles and permissions vary.

Ask your assistantTools and resultYour control
“Which open defects could block this release?”getWorkItems, getWorkItem: a scoped list of severity, owners and missing information.Read-only triage; approve any later reassignment.
“Review this LiveDoc and propose clearer acceptance criteria for REQ-17.”getDocument, getDocumentParts, getWorkItem, patchWorkItem: a rewrite of the requirement’s description.Preview with dry_run: true; approve before saving.
“Draft tests from these requirements, then record the results I provide.”getWorkItems, postWorkItems, postTestRuns, postTestRecords: proposed cases and a run, then supplied outcomes.Check existing tests, preview each write and approve. The connector does not execute product tests.
“Summarize this release plan and its latest test runs.”getPlan, getWorkItems, getTestRuns: a draft status update with source IDs and missing data.You decide release readiness.
“Find requirements without a verifies link to a test case.”getWorkItems, getLinkedWorkItems: a scoped gap list and existing candidate tests.Confirm link roles and scope before creating anything.

Explore the chat-style walkthroughs.

Get connected

Python users can use the Python launcher (uvx polarion-alm-mcp or pip install polarion-alm-mcp), which starts the matching npm release and requires Node.js 22+ and npm/npx. The PyPI package named polarion-mcp belongs to another project.

Two setups, pick by where your client runs. You need a REST-enabled Polarion instance and a PAT. Every guide starts from nothing and ends with a check.

SetupUse it whenGuide
Local (npm / npx)Your desktop or coding client runs on your computer and starts MCP servers.Local setup
Server (Docker)Your client runs in the cloud (claude.ai, ChatGPT) or your team shares one server.Server setup

Then open the guide for your client:

ClientLocalServerGuide
Claude DesktopYes (docs)Yes (docs)Open guide
claude.aiNoYes (docs)Open guide
Claude CodeYes (docs)Yes (docs)Open guide
Claude APINoYes (docs)Open guide
ChatGPT connectorNoYes (docs)Open guide
Custom GPT ActionsNoYes (docs)Open guide
OpenAI Responses APINoYes (docs)Open guide
OpenAI Agents SDKYes (docs)Yes (docs)Open guide
CodexYes (docs)Yes (docs)Open guide
Microsoft Copilot StudioNoYes (docs)Open guide
GitHub CopilotYes (docs)Yes (docs)Open guide
Antigravity (CLI + IDE)Yes (docs)Yes (docs)Open guide
Gemini (Enterprise)NoYes (docs)Open guide
CursorYes (docs)Yes (docs)Open guide
Windsurf / CascadeYes (docs)Yes (docs)Open guide
JetBrains AI AssistantYes (docs)NoOpen guide
Docker team serverNoYes (docs)Open guide
Other MCP client (starts a local program)Yes (docs)Yes (docs)Open guide
Other MCP client (connects by URL)NoYes (docs)Open guide
REST wrapper / OpenAPINoYes (docs)Open guide
n8n REST workflowNoYes (docs)Open guide
Microsoft 365 Copilot / TeamsNoYes (docs)Open guide
Mistral Le ChatNoYes (docs)Open guide
Open WebUI or LibreChat with your own modelsNoYes (docs)Open guide
Ollama with Open WebUI or LibreChatNoYes (docs)Open guide
vLLM with Open WebUI or LibreChatNoYes (docs)Open guide
OpenRouter with Open WebUI or LibreChatNoYes (docs)Open guide

For OpenAPI clients, Custom GPT Actions and n8n, run the separate REST wrapper (see the client guides). Keep credentials out of Git. There is no public Polarion relay. See also the client index and deployment.

FAQ

Which setup do I need?

Local: your client starts the server on your computer with npx. Server: you host the server with Docker and the client connects by URL; claude.ai and ChatGPT need it. Custom GPT Actions and n8n use the REST wrapper on a server.

How do I create a Polarion personal access token (PAT)?

Polarion user page > Personal Access Token > name and expiry > Create Token. Copy it at once, it is shown only once. If the page says token generation is not allowed, your administrator must enable com.siemens.polarion.rest.security.restApiToken.enabled=true.

Is my data safe? Which permissions apply?

Polarion enforces the permissions of the token owner. Server mode uses each caller's own token and the server stores none. Tool results go to your AI provider, so your organization's data policies apply.

Can I limit the server to read-only?

Yes: set MCP_READ_ONLY=1 and restart. Only read tools are exposed. In write-enabled sessions every write tool can preview with dry_run: true.

My AI client says "Disconnected" or "Failed to connect".

Local: run npx -y polarion-mcp in a terminal with the same values to see the real error (Node older than 22 and JSON typos are common). Server: open https://YOUR-SERVER/health, then read docker logs polarion-mcp.

More answers: docs/clients.md.

Feedback and community

Feedback and questions: open an issue. Include what you tried, your client and server mode, and what you expected. Leave credentials out.

Nothing documented for your case? Open an issue or PR on the repo and go wild. A clearer example, a small fix or a new integration can help the next team. Read Contributing for source builds and checks. Report vulnerabilities through the security policy.

Built by Phillip Bösger, building on @Jonasdero.

Documentation

Docs index · Configuration · Deployment · Security · Usage · Architecture · Extensions · Releases

Publishing and discovery · Official MCP Registry · Glama listing

License

MIT © Phillip Bösger

Source: README.md at commit 22d372f

Tools

200

branchDocument

Creates a branched LiveDoc and returns an asynchronous `jobs` resource. `requestBody.documentConfigurations` identifies the source and optional target project, space, and document name; omit target project/space to branch within the source project and space. Requires read access to the source and write access to the target; poll `getJob` for completion. Use `copyDocument` when branch lineage is not needed. Effect: triggers a server-side action rather than a plain resource creation — whether repeating it is safe, a no-op, or rejected depends on the specific action; treat it as 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.

Parametersdry_runspaceIdrequiredrevisionprojectIdrequiredrequestBodyrequireddocumentNamerequired

branchDocuments

Creates branches for multiple source LiveDocs and returns an asynchronous `jobs` resource. Each `documentConfigurations` entry supplies a source and may specify its own target; omitted targets stay with the source location. Requires source read and target write permissions; poll `getJob` for completion. Use `branchDocument` for one document. Effect: triggers a server-side action rather than a plain resource creation — whether repeating it is safe, a no-op, or rejected depends on the specific action; treat it as 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.

Parametersdry_runrequestBodyrequired

closeCollection

Closes one Collection, changing its lifecycle state while retaining its contents. Requires permission to update the Collection. Use `reopenCollection` to make a closed Collection active again, or `reuseCollection` when continuing its contents as a new cycle. Effect: triggers a server-side action rather than a plain resource creation — whether repeating it is safe, a no-op, or rejected depends on the specific action; treat it as 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.

Parametersdry_runprojectIdrequiredcollectionIdrequired

copyDocument

Copies one LiveDoc into a target project and space, creating a new document while leaving the source unchanged. Supply the target location and new document name in `requestBody`; omit target project/space only when the operation should remain in the source location. Use `branchDocument` when the copy must retain branch lineage. Effect: triggers a server-side action rather than a plain resource creation — whether repeating it is safe, a no-op, or rejected depends on the specific action; treat it as 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.

Parametersdry_runspaceIdrequiredrevisionprojectIdrequiredrequestBodyrequireddocumentNamerequired

createProject

Creates a new Polarion project and returns the created project resource. Supply a unique project ID and any required template configuration; the signed-in user must have project creation permission. Use `getProjectTemplates` first when selecting a template, or `markProject` to register existing repository data as a project. Effect: triggers a server-side action rather than a plain resource creation — whether repeating it is safe, a no-op, or rejected depends on the specific action; treat it as 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.

Parametersdry_runrequestBodyrequired

deleteAllWorkItems

Deletes a list of Work Items from the Global context. Scope: spans every project (no project filter). To act on a single project, use `deleteWorkItems` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runrequestBodyrequired

deleteApproval

Deletes the specified Work Item Approval. Cardinality: targets a single item by ID. For the full collection or a batch, use `deleteApprovals` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

ParametersuserIdrequireddry_runprojectIdrequiredworkItemIdrequired

deleteApprovals

Deletes a list of Work Item Approvals. Cardinality: targets the full collection or a batch. For a single item by ID, use `deleteApproval` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredworkItemIdrequiredrequestBodyrequired

deleteCollection

Deletes the specified Collection. Cardinality: targets a single item by ID. For the full collection or a batch, use `deleteCollections` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredcollectionIdrequired

deleteCollections

Deletes a list of Collections. Cardinality: targets the full collection or a batch. For a single item by ID, use `deleteCollection` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredrequestBodyrequired

deleteCollectionsRelationship

Removes the named relationship from one Collection; the related resource itself is not deleted. Read current links with `getCollectionsRelationship`; use `postCollectionsRelationships` to add links or `patchCollectionsRelationships` to replace the relationship set. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredrequestBodyrequiredcollectionIdrequiredrelationshipIdrequired

deleteDocumentParts

Deletes a list of Document Parts. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runspaceIdrequiredprojectIdrequiredrequestBodyrequireddocumentNamerequired

deleteExternallyLinkedWorkItem

Deletes the specified Externally Linked Work Item. Cardinality: targets a single item by ID. For the full collection or a batch, use `deleteExternallyLinkedWorkItems` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

ParametersroleIdrequireddry_runhostnamerequiredprojectIdrequiredworkItemIdrequiredtargetProjectIdrequiredlinkedWorkItemIdrequired

deleteExternallyLinkedWorkItems

Deletes a list of Externally Linked Work Items. Cardinality: targets the full collection or a batch. For a single item by ID, use `deleteExternallyLinkedWorkItem` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredworkItemIdrequiredrequestBodyrequired

deleteGlobalCustomFields

Deletes the specified Custom Field configuration from the Global context. Scope: spans every project (no project filter). To act on a single project, use `deleteProjectCustomFields` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runtargetTyperequiredresourceTyperequired

deleteGlobalEnumeration

Deletes the specified Enumeration from the Global context. Scope: spans every project (no project filter). To act on a single project, use `deleteProjectEnumeration` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runenumNamerequiredtargetTyperequiredenumContextrequired

deleteLicenseSlots

Deletes specified license slots from the Polarion server. This is a server-wide administrative change requiring license administration permission. Read current assignments with `getLicenseSlots` and capacity with `getLicense` before removal. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

ParameterstypeIdrequireddry_runrequestBodyrequired

deleteLinkedWorkItem

Deletes the direct outgoing links to other Work Items. (The same as the corresponding Java API method.) Does not pertain to external links or backlinks. Cardinality: targets a single item by ID. For the full collection or a batch, use `deleteLinkedWorkItems` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

ParametersroleIdrequireddry_runprojectIdrequiredworkItemIdrequiredtargetProjectIdrequiredlinkedWorkItemIdrequired

deleteLinkedWorkItems

Deletes the direct outgoing links to other Work Items. (The same as the corresponding Java API method.) Does not pertain to external links or backlinks. Cardinality: targets the full collection or a batch. For a single item by ID, use `deleteLinkedWorkItem` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredworkItemIdrequiredrequestBodyrequired

deleteOslcResources

Removes one or more OSLC links from a Work Item, identified in `requestBody.data` by their link IDs as returned by `getOslcResources`. Only the link is removed; the artifact in the remote OSLC tool is untouched. To add links use `postOslcResources`; for Polarion-internal links use `deleteLinkedWorkItems`. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredworkItemIdrequiredrequestBodyrequired

deletePage

Permanently deletes one Rich Page and its content; this cannot be undone through this API. Requires page deletion permission. Use `dry_run` to preview the request or `patchRichPage` to edit without deleting. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runspaceIdrequiredpageNamerequiredprojectIdrequired

deletePageAttachment

Deletes the specified Page Attachment. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runspaceIdrequiredpageNamerequiredprojectIdrequiredattachmentIdrequired

deletePageRelationships

Deletes a list of Page Relationships. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runspaceIdrequiredpageNamerequiredprojectIdrequiredrequestBodyrequiredrelationshipIdrequired

deletePlan

Deletes the specified Plan. Cardinality: targets a single item by ID. For the full collection or a batch, use `deletePlans` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

ParametersplanIdrequireddry_runprojectIdrequired

deletePlanRelationship

Removes the named relationship from one Plan without deleting the related resource. Read current links with `getPlanRelationship`; use `postPlanRelationships` to add links or `patchPlanRelationships` to replace them. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

ParametersplanIdrequireddry_runprojectIdrequiredrequestBodyrequiredrelationshipIdrequired

deletePlans

Deletes a list of Plans. Cardinality: targets the full collection or a batch. For a single item by ID, use `deletePlan` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredrequestBodyrequired

deleteProject

Permanently deletes a Polarion project and its project data, including contained resources; this cannot be recovered through the API. Requires project deletion permission. Use `dry_run` to preview the request, and use `unmarkProject` when the project data should remain in the repository. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequired

deleteProjectCustomFields

Deletes the specified Custom Field configuration from the Project context. Scope: one project (requires a project ID). To act across all projects, use `deleteGlobalCustomFields` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredtargetTyperequiredresourceTyperequired

deleteProjectEnumeration

Deletes the specified Enumeration from the Project context. Scope: one project (requires a project ID). To act across all projects, use `deleteGlobalEnumeration` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runenumNamerequiredprojectIdrequiredtargetTyperequiredenumContextrequired

deleteProjectTestParameterDefinition

Deletes the specified Test Parameter Definition for the specified Project. Cardinality: targets a single item by ID. For the full collection or a batch, use `deleteProjectTestParameterDefinitions` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredtestParamIdrequired

deleteProjectTestParameterDefinitions

Deletes a list of Test Parameter Definitions for the specified Project. Cardinality: targets the full collection or a batch. For a single item by ID, use `deleteProjectTestParameterDefinition` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredrequestBodyrequired

deleteTestRecord

Deletes one Test Record execution in a Test Run iteration, not the Test Case definition. Use `getTestRecords` to identify the record and `patchTestRecord` when only its values should change. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runiterationrequiredprojectIdrequiredtestRunIdrequiredtestCaseIdrequiredtestCaseProjectIdrequired

deleteTestRecordAttachment

Deletes the specified Test Record Attachment. Cardinality: targets a single item by ID. For the full collection or a batch, use `deleteTestRecordAttachments` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runiterationrequiredprojectIdrequiredtestRunIdrequiredtestCaseIdrequiredattachmentIdrequiredtestCaseProjectIdrequired

deleteTestRecordAttachments

Deletes a list of Test Record Attachments. Cardinality: targets the full collection or a batch. For a single item by ID, use `deleteTestRecordAttachment` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runiterationrequiredprojectIdrequiredtestRunIdrequiredtestCaseIdrequiredrequestBodyrequiredtestCaseProjectIdrequired

deleteTestRecordTestParameter

Removes one parameter value from a Test Record execution without deleting the record or Test Case. Use `getTestRecordTestParameters` to inspect values and `patchTestRecordTestParameters` to change rather than remove them. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runiterationrequiredprojectIdrequiredtestRunIdrequiredtestCaseIdrequiredtestParamIdrequiredtestCaseProjectIdrequired

deleteTestRun

Deletes the specified Test Run. Cardinality: targets a single item by ID. For the full collection or a batch, use `deleteTestRuns` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredtestRunIdrequired

deleteTestRunAttachment

Deletes the specified Test Run Attachment. Cardinality: targets a single item by ID. For the full collection or a batch, use `deleteTestRunAttachments` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredtestRunIdrequiredattachmentIdrequired

deleteTestRunAttachments

Deletes a list of Test Run Attachments. Cardinality: targets the full collection or a batch. For a single item by ID, use `deleteTestRunAttachment` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredtestRunIdrequiredrequestBodyrequired

deleteTestRunTestParameter

Deletes the specified Test Parameter for the specified Test Run. Cardinality: targets a single item by ID. For the full collection or a batch, use `deleteTestRunTestParameters` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredtestRunIdrequiredtestParamIdrequired

deleteTestRunTestParameterDefinition

Deletes the specified Test Parameter Definition for the specified Test Run. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredtestRunIdrequiredtestParamIdrequired

deleteTestRunTestParameters

Deletes a list of Test Parameters for the specified Test Run. Cardinality: targets the full collection or a batch. For a single item by ID, use `deleteTestRunTestParameter` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredtestRunIdrequiredrequestBodyrequired

deleteTestRuns

Deletes a list of Test Runs. Cardinality: targets the full collection or a batch. For a single item by ID, use `deleteTestRun` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredrequestBodyrequired

deleteTestStep

Deletes the specified Test Step. Cardinality: targets a single item by ID. For the full collection or a batch, use `deleteTestSteps` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredworkItemIdrequiredtestStepIndexrequired

deleteTestStepResultAttachment

Deletes the specified Test Step Result Attachment. Cardinality: targets a single item by ID. For the full collection or a batch, use `deleteTestStepResultAttachments` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runiterationrequiredprojectIdrequiredtestRunIdrequiredtestCaseIdrequiredattachmentIdrequiredtestStepIndexrequiredtestCaseProjectIdrequired

deleteTestStepResultAttachments

Deletes a list of Test Step Result Attachments. Cardinality: targets the full collection or a batch. For a single item by ID, use `deleteTestStepResultAttachment` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runiterationrequiredprojectIdrequiredtestRunIdrequiredtestCaseIdrequiredrequestBodyrequiredtestStepIndexrequiredtestCaseProjectIdrequired

deleteTestSteps

Deletes a list of Test Steps. Cardinality: targets the full collection or a batch. For a single item by ID, use `deleteTestStep` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredworkItemIdrequiredrequestBodyrequired

deleteWorkItemAttachment

Deletes the specified Work Item Attachment. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredworkItemIdrequiredattachmentIdrequired

deleteWorkItems

Deletes a list of Work Items. Scope: one project (requires a project ID). To act across all projects, use `deleteAllWorkItems` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredrequestBodyrequired

deleteWorkItemsRelationship

Removes one named JSON:API relationship from a Work Item; this edits linkage and does not delete related Work Items. Use `getWorkItemsRelationships` to inspect raw linkage or linked-work-item tools for link roles and related item details. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredworkItemIdrequiredrequestBodyrequiredrelationshipIdrequired

deleteWorkRecord

Deletes the specified Work Record. Cardinality: targets a single item by ID. For the full collection or a batch, use `deleteWorkRecords` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredworkItemIdrequiredworkRecordIdrequired

deleteWorkRecords

Deletes a list of Work Records. Cardinality: targets the full collection or a batch. For a single item by ID, use `deleteWorkRecord` instead. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredworkItemIdrequiredrequestBodyrequired

executeJob

Starts a Polarion asynchronous job and returns its `jobs` resource; this response means the job was accepted, not that it finished. Poll `getJob` with the returned job ID, then use `getJobLogContent` or `getJobResultFileContent` after completion. Use `run_job_and_wait` when bounded polling and a log tail are preferred. Effect: triggers a server-side action rather than a plain resource creation — whether repeating it is safe, a no-op, or rejected depends on the specific action; treat it as 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.

Parametersdry_runrequestBodyrequired

generateCompletion

Generates a chat completion using a Large Language Model (LLM). Effect: triggers a server-side action rather than a plain resource creation — whether repeating it is safe, a no-op, or rejected depends on the specific action; treat it as 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.

Parametersdry_runrequestBodyrequired

getAllDocuments

Returns a list of Documents from all Projects. Scope: spans every project (no project filter). To act on a single project, use `getDocuments` instead. Examples: {"query":"title:Plan","page[size]":20}. Selection: Use getAllDocuments to search Documents across projects; use getDocuments when listing within one project and getDocument when you know the Document name and need one result.

Parameterssortqueryfieldsincluderevisionmax_itemspage_size_page_number_response_format

getAllPages

Returns a list of Pages from all Projects and Pages on the Repository level. Scope: spans every project (no project filter). To act on a single project, use `getPages` instead.

Parameterssortqueryfieldsincluderevisionmax_itemspage_size_page_number_response_format

getAllWorkItems

Returns a list of Work Items from all Projects. Scope: spans every project (no project filter). To act on a single project, use `getWorkItems` instead. Examples: {"query":"type:requirement","fields":{"workitems":"id,title"},"page[size]":25}. Selection: Use getAllWorkItems when the search must span every project; use getWorkItems when you know the project and want a project-scoped result.

Parameterssortqueryfieldsincluderevisionmax_itemspage_size_page_number_response_format

getAvailableEnumOptionsForDocument

Returns the enumeration options that may be set on one field of one existing Document (ID, name, color/icon), narrowed by that Document's type. `fieldId` must be an enumeration-typed field (e.g. `status`, `severity`, or a custom enum field). Call it before patchDocument to pick a valid value; for the value(s) currently set use `getCurrentEnumerationOptionsForDocument`, and for a Document that does not exist yet use `getAvailableEnumOptionsForDocumentType`.

ParametersfieldIdrequiredspaceIdrequiredmax_itemsprojectIdrequiredpage_size_documentNamerequiredpage_number_response_format

getAvailableEnumOptionsForDocumentType

Returns the enumeration options that may be set on one field for a Document type (e.g. `type=req_specification`), before any concrete Document exists. `fieldId` must be an enumeration-typed field (e.g. `status`, `severity`, or a custom enum field). Pass `type=~` for options that apply regardless of type. Call it before postDocuments to choose valid values; for an existing Document use `getAvailableEnumOptionsForDocument`.

ParameterstypefieldIdrequiredmax_itemsprojectIdrequiredpage_size_page_number_response_format

getAvailableEnumOptionsForWorkItem

Returns the enumeration options that may be set on one field of one existing Work Item (ID, name, and presentation such as color/icon), already narrowed by that item's type and any dependent enumerations. `fieldId` must be an enumeration-typed field (e.g. `status`, `severity`, or a custom enum field). Call it before patchWorkItem to pick a valid value; for the value(s) currently set use `getCurrentEnumOptionsForWorkItem`, and for an item that does not exist yet use `getAvailableEnumOptionsForWorkItemType`.

ParametersfieldIdrequiredmax_itemsprojectIdrequiredpage_size_workItemIdrequiredpage_number_response_format

getAvailableEnumOptionsForWorkItemType

Returns the enumeration options that may be set on one field for a Work Item type (e.g. `type=requirement`), before any concrete item exists. `fieldId` must be an enumeration-typed field (e.g. `status`, `severity`, or a custom enum field). Pass `type=~` for options that apply regardless of type. Call it before postWorkItems to choose valid values; for an existing item use `getAvailableEnumOptionsForWorkItem`, which also applies that item's dependent enumerations.

ParameterstypefieldIdrequiredmax_itemsprojectIdrequiredpage_size_page_number_response_format

getAvatar

Downloads the avatar image of one user. Images (PNG, JPEG, GIF, WebP) come back as image content, UTF-8 text files as text, and any other file (PDF, Office, ZIP) as an embedded base64 resource; files over 20 MB are refused. Since avatars are images, this is rarely useful to an agent; for a user's name, email, and other profile data use `getUser`, and to replace the image use `updateAvatar`.

ParametersuserIdrequiredresponse_format

getBacklinkedWorkItems

Returns Work Items with an incoming link to the specified Work Item, paginated. Use `getLinkedWorkItems` for outgoing links, `getExternallyLinkedWorkItem` for links to another Polarion server, or `getWorkItemsRelationships` for raw relationship linkage without linked item details.

Parametersfieldsincluderevisionmax_itemsprojectIdrequiredpage_size_workItemIdrequiredpage_number_response_format

getCollection

Returns the specified Collection. Cardinality: targets a single item by ID. For the full collection or a batch, use `getCollections` instead.

ParametersfieldsincluderevisionprojectIdrequiredcollectionIdrequiredresponse_format

getCollections

Returns a list of Collections. Cardinality: targets the full collection or a batch. For a single item by ID, use `getCollection` instead.

Parameterssortqueryfieldsincluderevisionmax_itemsprojectIdrequiredpage_size_page_number_response_format

getCollectionsRelationship

Returns the resource identifiers linked from one Collection through a single named relationship, as JSON:API linkage (`{type, id}` entries) without the related resources' attributes. `relationshipId` is the relationship's name, not an entry ID. Use this to inspect one relationship cheaply; to read the Collection with its related resources embedded, call its get tool with `include` instead. To change the relationship, use `postCollectionsRelationships` (add), `patchCollectionsRelationships` (replace), or `deleteCollectionsRelationship` (remove).

ParametersfieldsincluderevisionprojectIdrequiredpage_size_collectionIdrequiredpage_number_relationshipIdrequiredresponse_format

getComment

Returns the specified Work Item Comment. Cardinality: targets a single item by ID. For the full collection or a batch, use `getComments` instead.

ParametersfieldsincluderevisioncommentIdrequiredprojectIdrequiredworkItemIdrequiredresponse_format

getComments

Lists comments associated with one Work Item. Use `getDocumentComments` for a LiveDoc, `getPageComments` for a Rich Page, or `getTestRunComments` for a Test Run. Cardinality: targets the full collection or a batch. For a single item by ID, use `getComment` instead. Selection: Use getComments for comments on a Work Item; use getDocumentComments for comments on a Document.

Parametersfieldsincluderevisionmax_itemsprojectIdrequiredpage_size_workItemIdrequiredpage_number_response_format

getCurrentEnumOptionsForWorkItem

Returns the enumeration option(s) currently selected in one field of one Work Item, resolved to full option objects (ID, name, color/icon) rather than the bare ID stored on the item. `fieldId` must be an enumeration-typed field (e.g. `status`, `severity`, or a custom enum field). Use it to display or compare the current value; for the options you could switch to use `getAvailableEnumOptionsForWorkItem`.

ParametersfieldIdrequiredrevisionmax_itemsprojectIdrequiredpage_size_workItemIdrequiredpage_number_response_format

getCurrentEnumerationOptionsForDocument

Returns the enumeration option(s) currently selected in one field of one Document, resolved to full option objects (ID, name, color/icon) rather than the bare stored ID. `fieldId` must be an enumeration-typed field (e.g. `status`, `severity`, or a custom enum field). Use it to display or compare the current value; for the options you could switch to use `getAvailableEnumOptionsForDocument`.

ParametersfieldIdrequiredspaceIdrequiredrevisionmax_itemsprojectIdrequiredpage_size_documentNamerequiredpage_number_response_format

getCurrentUser

Returns the Polarion user represented by the bearer token or active session, including that user’s profile fields. The result depends on the credentials used for this request and is not an arbitrary user lookup; use `getUser` with a user ID to inspect another profile. A 403 means the credentials cannot read this endpoint, not that authentication failed.

Parametersfieldsincluderevisionresponse_format

getDefaultIcon

Returns the specified Icon from the default context. Cardinality: targets a single item by ID. For the full collection or a batch, use `getDefaultIcons` instead.

ParametersfieldsiconIdrequiredresponse_format

getDefaultIcons

Returns a list of Icons from the default context. Cardinality: targets the full collection or a batch. For a single item by ID, use `getDefaultIcon` instead.

Parametersfieldsmax_itemspage_size_page_number_response_format

getDocument

Returns the specified Document. Cardinality: targets a single item by ID. For the full collection or a batch, use `getSpaceDocuments` instead. Examples: {"projectId":"myproject","spaceId":"_default","documentName":"requirements","fields":{"documents":"id,title,homePageContent"}}. Selection: Use getDocument to read one Document by name; use getAllDocuments to search a collection across projects.

ParametersfieldsincludespaceIdrequiredrevisionprojectIdrequireddocumentNamerequiredresponse_format

getDocumentAttachment

Returns the specified Document Attachment. Cardinality: targets a single item by ID. For the full collection or a batch, use `getDocumentAttachments` instead.

ParametersfieldsincludespaceIdrequiredrevisionprojectIdrequiredattachmentIdrequireddocumentNamerequiredresponse_format

getDocumentAttachmentContent

Downloads the raw file content of one Document attachment. Images (PNG, JPEG, GIF, WebP) come back as image content, UTF-8 text files as text, and any other file (PDF, Office, ZIP) as an embedded base64 resource; files over 20 MB are refused. Use this only when you need the file's bytes; for its metadata (fileName, contentType, size, author) call `getDocumentAttachment`, and to discover attachment IDs call `getDocumentAttachments`.

ParametersspaceIdrequiredrevisionprojectIdrequiredattachmentIdrequireddocumentNamerequiredresponse_format

getDocumentAttachments

Returns a list of Document Attachments. Cardinality: targets the full collection or a batch. For a single item by ID, use `getDocumentAttachment` instead.

ParametersfieldsincludespaceIdrequiredrevisionmax_itemsprojectIdrequiredpage_size_documentNamerequiredpage_number_response_format

getDocumentComment

Returns the specified Document Comment. Cardinality: targets a single item by ID. For the full collection or a batch, use `getDocumentComments` instead.

ParametersfieldsincludespaceIdrequiredrevisioncommentIdrequiredprojectIdrequireddocumentNamerequiredresponse_format

getDocumentComments

Returns a list of Document Comments. Cardinality: targets the full collection or a batch. For a single item by ID, use `getDocumentComment` instead. Selection: Use getDocumentComments for comments on a Document; use getComments for comments on a Work Item.

ParametersfieldsincludespaceIdrequiredrevisionmax_itemsprojectIdrequiredpage_size_documentNamerequiredpage_number_response_format

getDocumentPart

Returns the specified Document Part. Cardinality: targets a single item by ID. For the full collection or a batch, use `getDocumentParts` instead.

ParametersfieldspartIdrequiredincludespaceIdrequiredrevisionprojectIdrequireddocumentNamerequiredresponse_format

getDocumentParts

Returns a list of Document Parts. Cardinality: targets the full collection or a batch. For a single item by ID, use `getDocumentPart` instead.

ParametersfieldsincludespaceIdrequiredrevisionmax_itemsprojectIdrequiredpage_size_documentNamerequiredpage_number_response_format

getDocuments

Returns a list of Documents from the Project context. Scope: one project (requires a project ID). To act across all projects, use `getAllDocuments` instead. Examples: {"projectId":"myproject","query":"title:Plan","page[size]":20}. Selection: Use getDocuments when listing Documents in one project; use getAllDocuments to search across projects.

Parameterssortqueryfieldsincluderevisionmax_itemsprojectIdrequiredpage_size_page_number_response_format

getExportExcelTests

Starts an asynchronous export of one Test Run's test cases to an Excel workbook, optionally filtered with `query`, ordered with `sortBy`, and shaped by an export `template`. Returns a `jobs` resource, not the file: poll `getJob` until finished, then download the workbook with `getJobResultFileContent`. To import results back, use `importExcelTestResults`.

ParametersquerysortBytemplateprojectIdrequiredtestRunIdrequiredresponse_format

getExternallyLinkedWorkItem

Returns Work Items linked to the specified item in another Polarion server, using the external-link relationship. Use `getLinkedWorkItems` or `getBacklinkedWorkItems` for links within this server and `getWorkItemsRelationships` for raw relationship identifiers. Cardinality: targets a single item by ID. For the full collection or a batch, use `getExternallyLinkedWorkItems` instead.

ParametersfieldsroleIdrequiredincludehostnamerequiredrevisionprojectIdrequiredworkItemIdrequiredresponse_formattargetProjectIdrequiredlinkedWorkItemIdrequired

getExternallyLinkedWorkItems

Returns the external links to other Work Items. (The same as the corresponding Java API method.). Cardinality: targets the full collection or a batch. For a single item by ID, use `getExternallyLinkedWorkItem` instead.

Parametersfieldsincluderevisionmax_itemsprojectIdrequiredpage_size_workItemIdrequiredpage_number_response_format

getFeatureSelection

Returns the specified Feature Selection. Cardinality: targets a single item by ID. For the full collection or a batch, use `getFeatureSelections` instead.

ParametersfieldsincluderevisionprojectIdrequiredworkItemIdrequiredresponse_formatselectionTypeIdrequiredtargetProjectIdrequiredtargetWorkItemIdrequired

getFeatureSelections

Returns a list of Feature Selections. Cardinality: targets the full collection or a batch. For a single item by ID, use `getFeatureSelection` instead.

Parametersfieldsincluderevisionmax_itemsprojectIdrequiredpage_size_workItemIdrequiredpage_number_response_format

getFieldsMetadataForCollection

Returns the field definitions that apply to one specific Collection, keyed by field ID: each field's label and type kind (primitive such as `string`/`date`/`text/html`, list, structure, or enumeration with its enum name), including the custom fields configured for its type. Use it before writing to the Collection to learn which field keys and value types are valid. For the project-wide definitions of a resource type without a concrete instance, use `getProjectFieldsMetadata`; for global defaults, `getGlobalFieldsMetadata`.

ParametersprojectIdrequiredcollectionIdrequiredresponse_format

getFieldsMetadataForDocument

Returns the field definitions that apply to one specific Document, keyed by field ID: each field's label and type kind (primitive such as `string`/`date`/`text/html`, list, structure, or enumeration with its enum name), including the custom fields configured for its type. Use it before writing to the Document to learn which field keys and value types are valid. For the allowed values of one enum field, follow up with `getAvailableEnumOptionsForDocument`. For the project-wide definitions of a resource type without a concrete instance, use `getProjectFieldsMetadata`; for global defaults, `getGlobalFieldsMetadata`.

ParametersspaceIdrequiredprojectIdrequireddocumentNamerequiredresponse_format

getFieldsMetadataForPlan

Returns the field definitions that apply to one specific Plan, keyed by field ID: each field's label and type kind (primitive such as `string`/`date`/`text/html`, list, structure, or enumeration with its enum name), including the custom fields configured for its type. Use it before writing to the Plan to learn which field keys and value types are valid. For the project-wide definitions of a resource type without a concrete instance, use `getProjectFieldsMetadata`; for global defaults, `getGlobalFieldsMetadata`.

ParametersplanIdrequiredprojectIdrequiredresponse_format

getFieldsMetadataForTestRecord

Returns the field definitions that apply to one specific Test Record (one test case execution within a Test Run iteration), keyed by field ID: each field's label and type kind (primitive such as `string`/`date`/`text/html`, list, structure, or enumeration with its enum name), including the custom fields configured for its type. Use it before writing to the Test Record (one test case execution within a Test Run iteration) to learn which field keys and value types are valid. For the project-wide definitions of a resource type without a concrete instance, use `getProjectFieldsMetadata`; for global defaults, `getGlobalFieldsMetadata`.

ParametersiterationrequiredprojectIdrequiredtestRunIdrequiredtestCaseIdrequiredresponse_formattestCaseProjectIdrequired

getFieldsMetadataForTestRun

Returns the field definitions that apply to one specific Test Run, keyed by field ID: each field's label and type kind (primitive such as `string`/`date`/`text/html`, list, structure, or enumeration with its enum name), including the custom fields configured for its type. Use it before writing to the Test Run to learn which field keys and value types are valid. For the project-wide definitions of a resource type without a concrete instance, use `getProjectFieldsMetadata`; for global defaults, `getGlobalFieldsMetadata`.

ParametersprojectIdrequiredtestRunIdrequiredresponse_format

getFieldsMetadataForWorkItem

Returns the field definitions that apply to one specific Work Item, keyed by field ID: each field's label and type kind (primitive such as `string`/`date`/`text/html`, list, structure, or enumeration with its enum name), including the custom fields configured for its type. Use it before writing to the Work Item to learn which field keys and value types are valid. For the allowed values of one enum field, follow up with `getAvailableEnumOptionsForWorkItem`. For the project-wide definitions of a resource type without a concrete instance, use `getProjectFieldsMetadata`; for global defaults, `getGlobalFieldsMetadata`.

ParametersprojectIdrequiredworkItemIdrequiredresponse_format

getGlobalCustomFields

Returns the defined Custom Fields for the resource type and target type in the Global context. Scope: spans every project (no project filter). To act on a single project, use `getProjectCustomFields` instead.

ParametersfieldsincludetargetTyperequiredresourceTyperequiredresponse_format

getGlobalEnumeration

Returns the specified Enumeration from the Global context. Scope: spans every project (no project filter). To act on a single project, use `getProjectEnumeration` instead. Cardinality: targets a single item by ID. For the full collection or a batch, use `getGlobalEnumerations` instead. Selection: Use getGlobalEnumeration for global enumeration values; use getProjectEnumeration for values configured in one project.

ParametersfieldsincludeenumNamerequiredtargetTyperequiredenumContextrequiredresponse_format

getGlobalEnumerations

Returns a list of Enumerations from the Global context. Scope: spans every project (no project filter). To act on a single project, use `getProjectEnumerations` instead. Cardinality: targets the full collection or a batch. For a single item by ID, use `getGlobalEnumeration` instead.

Parametersfieldsmax_itemspage_size_page_number_response_format

getGlobalFieldsMetadata

Returns fields for the resource type and its target type in the Global context. Scope: spans every project (no project filter). To act on a single project, use `getProjectFieldsMetadata` instead.

ParameterstargetTyperesourceTyperequiredresponse_format

getGlobalIcon

Returns the specified Icon from the Global context. Scope: spans every project (no project filter). To act on a single project, use `getProjectIcon` instead. Cardinality: targets a single item by ID. For the full collection or a batch, use `getGlobalIcons` instead.

ParametersfieldsiconIdrequiredresponse_format

getGlobalIcons

Returns a list of Icons from the Global context. Scope: spans every project (no project filter). To act on a single project, use `getProjectIcons` instead. Cardinality: targets the full collection or a batch. For a single item by ID, use `getGlobalIcon` instead.

Parametersfieldsmax_itemspage_size_page_number_response_format

getGlobalPages

Lists Rich Pages across repository spaces, subject to the signed-in user’s global repository read permissions; returns an empty page when no matching pages are visible. Use `getSpacePages` for a known space, `getRepositorySpacePages` for one repository space, or `getPages` for a project space. Follow pagination links or use `max_items` to cap collection.

Parameterssortqueryfieldsincludemax_itemspage_size_page_number_response_format

getJob

Returns the specified Job. Cardinality: targets a single item by ID. For the full collection or a batch, use `getJobs` instead. Examples: {"jobId":"job-123"}.

ParametersjobIdrequiredfieldsincluderesponse_format

getJobLogContent

Downloads the plain-text execution log for one asynchronous Polarion job. Call after `getJob` reports a terminal state because a running job may have an incomplete log; `jobId` comes from the `jobs` resource returned by the operation that started it. Use `getJobResultFileContent` for produced files instead of logs.

ParametersjobIdrequiredresponse_format

getJobResultFileContent

Downloads one result file produced by a finished asynchronous job (e.g. the spreadsheet from getExportExcelTests). Images (PNG, JPEG, GIF, WebP) come back as image content, UTF-8 text files as text, and any other file (PDF, Office, ZIP) as an embedded base64 resource; files over 20 MB are refused. Call it only after `getJob` reports the job as finished; the job resource lists the available file names. For the job's log instead of its output, use `getJobLogContent`.

ParametersjobIdrequiredfilenamerequiredresponse_format

getJobs

Returns the list of Jobs. Cardinality: targets the full collection or a batch. For a single item by ID, use `getJob` instead.

Parametersfieldsincludemax_itemsprojectIdpage_size_page_number_response_format

getLicense

Returns the server-wide license limits as current count vs. maximum for Work Items, Documents/Pages, and projects, plus links to the default license slots. Use it to check remaining capacity before bulk-creating items or projects; for which user holds which license use `getLicenseAssignments`, and for the slot details `getLicenseSlots`.

Parametersfieldsincluderesponse_format

getLicenseAssignments

Returns a list of License Assignments. (Not supported by cloud-based Polarion X.). Cardinality: targets the full collection or a batch. For a single item by ID, use `getLicenseAssignmentsForUser` instead.

Parametersfieldsincludemax_itemsactiveOnlypage_size_page_number_response_format

getLicenseAssignmentsForUser

Returns the specified License Assignment. (Not supported by cloud-based Polarion X.). Cardinality: targets a single item by ID. For the full collection or a batch, use `getLicenseAssignments` instead.

ParametersfieldsuserIdrequiredincluderesponse_format

getLicenseSlot

Returns the specified License Slot. (Not supported by cloud-based Polarion X.). Cardinality: targets a single item by ID. For the full collection or a batch, use `getLicenseSlots` instead.

ParametersgrouprequiredmodelrequiredfieldstypeIdrequiredincluderesponse_format

getLicenseSlots

Returns information on the available License Slots. (Not supported by cloud-based Polarion X.). Cardinality: targets the full collection or a batch. For a single item by ID, use `getLicenseSlot` instead.

ParametersfieldstypeIdrequiredincluderevisionmax_itemspage_size_page_number_response_format

getLinkedWorkItem

Returns the direct outgoing links to other Work Items. (The same as the corresponding Java API method.) Does not pertain to external links or backlinks. Cardinality: targets a single item by ID. For the full collection or a batch, use `getLinkedWorkItems` instead.

ParametersfieldsroleIdrequiredincluderevisionprojectIdrequiredworkItemIdrequiredresponse_formattargetProjectIdrequiredlinkedWorkItemIdrequired

getLinkedWorkItems

Returns the direct outgoing links to other Work Items. (The same as the corresponding Java API method.) Does not pertain to external links or backlinks. Cardinality: targets the full collection or a batch. For a single item by ID, use `getLinkedWorkItem` instead.

Parametersfieldsincluderevisionmax_itemsprojectIdrequiredpage_size_workItemIdrequiredpage_number_response_format

getLlms

Returns the Large Language Models configured on this Polarion server for its built-in AI features (ID and name), paginated. Call it before `generateCompletion` to pick a valid model; an empty list means no LLM is configured and AI actions will fail.

Parameterspage_size_page_number_response_format

getMetadata

Returns server-wide Polarion REST metadata available to REST API users. Use this for global field/configuration definitions; use `getProjectFieldsMetadata` for a project’s effective resource fields and `getFieldsMetadataForWorkItem` for fields on a specific Work Item.

Parametersfieldsincluderesponse_format

getOslcResources

Returns the OSLC resources linked to one Work Item: links to artifacts in other OSLC-capable tools (e.g. Jira, DOORS Next, Teamcenter), each with its URI, label, and link role. Use it to trace cross-tool links; for links to Work Items in this or another Polarion server use `getLinkedWorkItems` or `getExternallyLinkedWorkItems`.

ParameterssortqueryfieldsincluderevisionprojectIdrequiredpage_size_workItemIdrequiredpage_number_response_format

getPage

Returns the specified Page. Cardinality: targets a single item by ID. For the full collection or a batch, use `getSpacePages` instead.

ParametersfieldsincludespaceIdrequiredpageNamerequiredrevisionprojectIdrequiredresponse_format

getPageAttachment

Returns the specified Page Attachment. Cardinality: targets a single item by ID. For the full collection or a batch, use `getPageAttachments` instead.

ParametersfieldsincludespaceIdrequiredpageNamerequiredrevisionprojectIdrequiredattachmentIdrequiredresponse_format

getPageAttachmentContent

Downloads the raw file content of one Rich Page attachment. Images (PNG, JPEG, GIF, WebP) come back as image content, UTF-8 text files as text, and any other file (PDF, Office, ZIP) as an embedded base64 resource; files over 20 MB are refused. Use this only when you need the file's bytes; for its metadata (fileName, contentType, size, author) call `getPageAttachment`, and to discover attachment IDs call `getPageAttachments`.

ParametersspaceIdrequiredpageNamerequiredrevisionprojectIdrequiredattachmentIdrequiredresponse_format

getPageAttachments

Returns a list of Page Attachments. Cardinality: targets the full collection or a batch. For a single item by ID, use `getPageAttachment` instead.

ParametersfieldsincludespaceIdrequiredpageNamerequiredrevisionmax_itemsprojectIdrequiredpage_size_page_number_response_format

getPageComment

Returns the specified Page Comment. Cardinality: targets a single item by ID. For the full collection or a batch, use `getPageComments` instead.

ParametersfieldsincludespaceIdrequiredpageNamerequiredrevisioncommentIdrequiredprojectIdrequiredresponse_format

getPageComments

Returns a list of Page Comments. Cardinality: targets the full collection or a batch. For a single item by ID, use `getPageComment` instead.

ParametersfieldsincludespaceIdrequiredpageNamerequiredrevisionmax_itemsprojectIdrequiredpage_size_page_number_response_format

getPageRelationships

Returns the resource identifiers linked from one Rich Page through a single named relationship, as JSON:API linkage (`{type, id}` entries) without the related resources' attributes. `relationshipId` is the relationship's name, not an entry ID. Use this to inspect one relationship cheaply; to read the Rich Page with its related resources embedded, call its get tool with `include` instead. To change the relationship, use `postPageRelationships` (add), `patchPageRelationships` (replace), or `deletePageRelationships` (remove).

ParametersfieldsincludespaceIdrequiredpageNamerequiredrevisionprojectIdrequiredpage_size_page_number_relationshipIdrequiredresponse_format

getPages

Returns a list of Pages from the Project context. Scope: one project (requires a project ID). To act across all projects, use `getAllPages` instead.

Parameterssortqueryfieldsincluderevisionmax_itemsprojectIdrequiredpage_size_page_number_response_format

getPlan

Returns the specified Plan. Cardinality: targets a single item by ID. For the full collection or a batch, use `getPlans` instead.

ParametersfieldsplanIdrequiredincluderevisionprojectIdrequiredresponse_format

getPlanRelationship

Returns the resource identifiers linked from one Plan through a single named relationship, as JSON:API linkage (`{type, id}` entries) without the related resources' attributes. `relationshipId` is the relationship's name, not an entry ID. Use this to inspect one relationship cheaply; to read the Plan with its related resources embedded, call its get tool with `include` instead. To change the relationship, use `postPlanRelationships` (add), `patchPlanRelationships` (replace), or `deletePlanRelationship` (remove).

ParametersfieldsplanIdrequiredincluderevisionprojectIdrequiredpage_size_page_number_relationshipIdrequiredresponse_format

getPlans

Returns a list of Plans. Cardinality: targets the full collection or a batch. For a single item by ID, use `getPlan` instead.

Parameterssortqueryfieldsincluderevisionmax_itemsprojectIdrequiredtemplatespage_size_page_number_response_format

getProject

Returns the specified Project. Cardinality: targets a single item by ID. For the full collection or a batch, use `getProjects` instead.

ParametersfieldsincluderevisionprojectIdrequiredresponse_format

getProjectCustomFields

Returns the defined Custom Fields for the resource type and target type in the Project context. Scope: one project (requires a project ID). To act across all projects, use `getGlobalCustomFields` instead.

ParametersfieldsincludeprojectIdrequiredtargetTyperequiredresourceTyperequiredresponse_format

getProjectEnumeration

Returns the specified Enumeration from the Project context. Scope: one project (requires a project ID). To act across all projects, use `getGlobalEnumeration` instead. Cardinality: targets a single item by ID. For the full collection or a batch, use `getProjectEnumerations` instead. Examples: {"projectId":"myproject","enumContext":"workitems","enumName":"status","targetType":"requirement"}. Selection: Use getProjectEnumeration for values configured in one project; use getGlobalEnumeration for global enumeration values.

ParametersfieldsincludeenumNamerequiredprojectIdrequiredtargetTyperequiredenumContextrequiredresponse_format

getProjectEnumerations

Returns a list of Enumerations from the Project context. Scope: one project (requires a project ID). To act across all projects, use `getGlobalEnumerations` instead. Cardinality: targets the full collection or a batch. For a single item by ID, use `getProjectEnumeration` instead. For the same collection across projects, use `getGlobalEnumerations` instead.

Parametersfieldsmax_itemsprojectIdrequiredpage_size_page_number_response_format

getProjectFieldsMetadata

Returns fields for the resource type and its target type in the Project context. Scope: one project (requires a project ID). To act across all projects, use `getGlobalFieldsMetadata` instead.

ParametersprojectIdrequiredtargetTyperesourceTyperequiredresponse_format

getProjectIcon

Returns the specified Icon from the Project context. Scope: one project (requires a project ID). To act across all projects, use `getGlobalIcon` instead. Cardinality: targets a single item by ID. For the full collection or a batch, use `getProjectIcons` instead.

ParametersfieldsiconIdrequiredprojectIdrequiredresponse_format

getProjectIcons

Returns a list of Icons from the Project context. Scope: one project (requires a project ID). To act across all projects, use `getGlobalIcons` instead. Cardinality: targets the full collection or a batch. For a single item by ID, use `getProjectIcon` instead. For the same collection across projects, use `getGlobalIcons` instead.

Parametersfieldsmax_itemsprojectIdrequiredpage_size_page_number_response_format

getProjectTemplates

Returns the project templates available on the server (ID, name, description, whether it is the default, and its parameters), paginated. Call it before `createProject` to choose a valid `templateId`.

Parametersfieldsincludemax_itemspage_size_page_number_response_format

getProjectTestParameterDefinition

Returns the specified Test Parameter Definition for the specified Project. Cardinality: targets a single item by ID. For the full collection or a batch, use `getProjectTestParameterDefinitions` instead.

ParametersfieldsincludeprojectIdrequiredtestParamIdrequiredresponse_format

getProjectTestParameterDefinitions

Returns a list of Test Parameter Definitions for the specified Project. Cardinality: targets the full collection or a batch. For a single item by ID, use `getProjectTestParameterDefinition` instead.

Parametersfieldsincludemax_itemsprojectIdrequiredpage_size_page_number_response_format

getProjects

Returns a list of Projects. Cardinality: targets the full collection or a batch. For a single item by ID, use `getProject` instead. Examples: {"query":"active:true","page[size]":20}.

Parameterssortqueryfieldsincluderevisionmax_itemspage_size_page_number_response_format

getRepositorySpacePages

Returns the Rich Pages in one space at the repository (server) level, outside any project, paginated and filterable with `query`. Use it for global wiki pages; for pages inside a project space use `getSpacePages`, and for every repository-level page regardless of space use `getGlobalPages`.

ParameterssortqueryfieldsincludespaceIdrequiredrevisionmax_itemspage_size_page_number_response_format

getRevision

Returns one repository revision (commit) by its number: author, timestamp, and commit message. Use it to see who changed data at a known revision, e.g. a `revision` value seen on a resource; to search or page through revision history use `getRevisions`. Cardinality: targets a single item by ID. For the full collection or a batch, use `getRevisions` instead.

ParametersfieldsincluderevisionrequiredrepositoryNamerequiredresponse_format

getRevisions

Returns repository revisions (commits) with author, timestamp, and commit message, paginated and filterable with `query`. Use it to audit recent changes across the repository; for one known revision number use `getRevision`. Cardinality: targets the full collection or a batch. For a single item by ID, use `getRevision` instead.

Parameterssortqueryfieldsincludemax_itemspage_size_page_number_response_format

getRole

Returns one global role (e.g. `admin`, `user`) and the users that hold it. Use it to check who has server-wide permissions; project-level roles are not covered by this tool. For a user's own profile and roles use `getUser`.

ParametersfieldsroleIdrequiredincluderesponse_format

getSpaceDocuments

Returns a list of Documents from a given Project Space. Cardinality: targets the full collection or a batch. For a single item by ID, use `getDocument` instead.

ParameterssortqueryfieldsincludespaceIdrequiredmax_itemsprojectIdrequiredpage_size_page_number_response_format

getSpacePages

Lists Rich Pages in the specified project space and returns the paginated JSON:API page collection. Requires a project ID and space ID visible to the signed-in user. Use `getGlobalPages` for pages across repository spaces or `getRepositorySpacePages` for a repository-level space outside projects. Cardinality: targets the full collection or a batch. For a single item by ID, use `getPage` instead.

ParameterssortqueryfieldsincludespaceIdrequiredmax_itemsprojectIdrequiredpage_size_page_number_response_format

getTestRecord

Returns the specified Test Record. Cardinality: targets a single item by ID. For the full collection or a batch, use `getTestRecords` instead.

ParametersfieldsincluderevisioniterationrequiredprojectIdrequiredtestRunIdrequiredtestCaseIdrequiredresponse_formattestCaseProjectIdrequired

getTestRecordAttachment

Returns the specified Test Record Attachment. Cardinality: targets a single item by ID. For the full collection or a batch, use `getTestRecordAttachments` instead.

ParametersfieldsincluderevisioniterationrequiredprojectIdrequiredtestRunIdrequiredtestCaseIdrequiredattachmentIdrequiredresponse_formattestCaseProjectIdrequired

getTestRecordAttachmentContent

Downloads the raw file content of one Test Record attachment. Images (PNG, JPEG, GIF, WebP) come back as image content, UTF-8 text files as text, and any other file (PDF, Office, ZIP) as an embedded base64 resource; files over 20 MB are refused. Use this only when you need the file's bytes; for its metadata (fileName, contentType, size, author) call `getTestRecordAttachment`, and to discover attachment IDs call `getTestRecordAttachments`.

ParametersrevisioniterationrequiredprojectIdrequiredtestRunIdrequiredtestCaseIdrequiredattachmentIdrequiredresponse_formattestCaseProjectIdrequired

getTestRecordAttachments

Returns a list of Test Record Attachments. Cardinality: targets the full collection or a batch. For a single item by ID, use `getTestRecordAttachment` instead.

Parametersfieldsincluderevisioniterationrequiredmax_itemsprojectIdrequiredtestRunIdrequiredpage_size_testCaseIdrequiredpage_number_response_formattestCaseProjectIdrequired

getTestRecordTestParameter

Returns the specified Test Parameter for the specified Test Record. Cardinality: targets a single item by ID. For the full collection or a batch, use `getTestRecordTestParameters` instead.

ParametersfieldsincluderevisioniterationrequiredprojectIdrequiredtestRunIdrequiredtestCaseIdrequiredtestParamIdrequiredresponse_formattestCaseProjectIdrequired

getTestRecordTestParameters

Returns a list of Test Parameters for the specified Test Record. Cardinality: targets the full collection or a batch. For a single item by ID, use `getTestRecordTestParameter` instead.

Parametersfieldsincluderevisioniterationrequiredmax_itemsprojectIdrequiredtestRunIdrequiredpage_size_testCaseIdrequiredpage_number_response_formattestCaseProjectIdrequired

getTestRecords

Returns a list of Test Records. Cardinality: targets the full collection or a batch. For a single item by ID, use `getTestRecord` instead.

Parametersfieldsincluderevisionmax_itemsprojectIdrequiredtestRunIdrequiredpage_size_testCaseIdpage_number_testResultIdresponse_formattestCaseProjectId

getTestRun

Returns the specified Test Run. Cardinality: targets a single item by ID. For the full collection or a batch, use `getTestRuns` instead. Examples: {"projectId":"myproject","testRunId":"Regression-2026-10"}.

ParametersfieldsincluderevisionprojectIdrequiredtestRunIdrequiredresponse_format

getTestRunAttachment

Returns metadata for one attachment on a Test Run, including its file name and content type. Use `getTestRunAttachmentContent` to download the bytes or `getTestRunAttachments` to list attachments. Cardinality: targets a single item by ID. For the full collection or a batch, use `getTestRunAttachments` instead.

ParametersfieldsincluderevisionprojectIdrequiredtestRunIdrequiredattachmentIdrequiredresponse_format

getTestRunAttachmentContent

Downloads one Test Run attachment and returns its file bytes as image, text, or embedded-resource content. Images (PNG, JPEG, GIF, WebP) come back as image content, UTF-8 text files as text, and any other file (PDF, Office, ZIP) as an embedded base64 resource; files over 20 MB are refused. Use `getTestRunAttachment` for metadata or `getTestRunAttachments` to list available attachment IDs; read the attachment only when its contents are needed.

ParametersrevisionprojectIdrequiredtestRunIdrequiredattachmentIdrequiredresponse_format

getTestRunAttachments

Lists attachment metadata on one Test Run. Use `getTestRunAttachment` for one known attachment ID and `getTestRunAttachmentContent` to read its file bytes. Cardinality: targets the full collection or a batch. For a single item by ID, use `getTestRunAttachment` instead.

Parametersfieldsincluderevisionmax_itemsprojectIdrequiredtestRunIdrequiredpage_size_page_number_response_format

getTestRunComment

Returns the specified Test Run Comment. Cardinality: targets a single item by ID. For the full collection or a batch, use `getTestRunComments` instead.

ParametersfieldsincluderevisioncommentIdrequiredprojectIdrequiredtestRunIdrequiredresponse_format

getTestRunComments

Returns a list of Test Run Comments. Cardinality: targets the full collection or a batch. For a single item by ID, use `getTestRunComment` instead.

Parametersfieldsincluderevisionmax_itemsprojectIdrequiredtestRunIdrequiredpage_size_page_number_response_format

getTestRunTestParameter

Returns the specified Test Parameter for the specified Test Run. Cardinality: targets a single item by ID. For the full collection or a batch, use `getTestRunTestParameters` instead.

ParametersfieldsincluderevisionprojectIdrequiredtestRunIdrequiredtestParamIdrequiredresponse_format

getTestRunTestParameterDefinition

Returns the specified Test Parameter Definition for the specified Test Run. Cardinality: targets a single item by ID. For the full collection or a batch, use `getTestRunTestParameterDefinitions` instead.

ParametersfieldsincluderevisionprojectIdrequiredtestRunIdrequiredtestParamIdrequiredresponse_format

getTestRunTestParameterDefinitions

Returns a list of Test Parameter Definitions for the specified Test Run. Cardinality: targets the full collection or a batch. For a single item by ID, use `getTestRunTestParameterDefinition` instead.

Parametersfieldsincluderevisionmax_itemsprojectIdrequiredtestRunIdrequiredpage_size_page_number_response_format

getTestRunTestParameters

Returns a list of Test Parameters for the specified Test Run. Cardinality: targets the full collection or a batch. For a single item by ID, use `getTestRunTestParameter` instead.

Parametersfieldsincluderevisionmax_itemsprojectIdrequiredtestRunIdrequiredpage_size_page_number_response_format

getTestRuns

Returns a list of Test Runs. Cardinality: targets the full collection or a batch. For a single item by ID, use `getTestRun` instead. Examples: {"projectId":"myproject","query":"status:inprogress","page[size]":20}.

Parameterssortqueryfieldsincluderevisionmax_itemsprojectIdrequiredtemplatespage_size_page_number_response_format

getTestStep

Returns the specified Test Step. Cardinality: targets a single item by ID. For the full collection or a batch, use `getTestSteps` instead.

ParametersfieldsincluderevisionprojectIdrequiredworkItemIdrequiredtestStepIndexrequiredresponse_format

getTestStepResult

Returns the specified Test Step Result. Cardinality: targets a single item by ID. For the full collection or a batch, use `getTestStepResults` instead.

ParametersfieldsincluderevisioniterationrequiredprojectIdrequiredtestRunIdrequiredtestCaseIdrequiredtestStepIndexrequiredresponse_formattestCaseProjectIdrequired

getTestStepResultAttachment

Returns the specified Test Step Result Attachment for the specified Test Record. Cardinality: targets a single item by ID. For the full collection or a batch, use `getTestStepResultAttachments` instead.

ParametersfieldsincluderevisioniterationrequiredprojectIdrequiredtestRunIdrequiredtestCaseIdrequiredattachmentIdrequiredtestStepIndexrequiredresponse_formattestCaseProjectIdrequired

getTestStepResultAttachmentContent

Downloads the raw file content of one Test Step Result attachment. Images (PNG, JPEG, GIF, WebP) come back as image content, UTF-8 text files as text, and any other file (PDF, Office, ZIP) as an embedded base64 resource; files over 20 MB are refused. Use this only when you need the file's bytes; for its metadata (fileName, contentType, size, author) call `getTestStepResultAttachment`, and to discover attachment IDs call `getTestStepResultAttachments`.

ParametersrevisioniterationrequiredprojectIdrequiredtestRunIdrequiredtestCaseIdrequiredattachmentIdrequiredtestStepIndexrequiredresponse_formattestCaseProjectIdrequired

getTestStepResultAttachments

Returns a list of Attachments for the specified Test Step Result. Cardinality: targets the full collection or a batch. For a single item by ID, use `getTestStepResultAttachment` instead.

Parametersfieldsincluderevisioniterationrequiredmax_itemsprojectIdrequiredtestRunIdrequiredpage_size_testCaseIdrequiredpage_number_testStepIndexrequiredresponse_format+1 more

getTestStepResults

Lists the execution results for steps in one Test Record, including result values and step references. Requires the project, Test Run, iteration, and Test Record identifiers. Use `getTestSteps` for the Test Case definition or `getTestRun` for overall execution status. Cardinality: targets the full collection or a batch. For a single item by ID, use `getTestStepResult` instead.

Parametersfieldsincluderevisioniterationrequiredmax_itemsprojectIdrequiredtestRunIdrequiredpage_size_testCaseIdrequiredpage_number_response_formattestCaseProjectIdrequired

getTestSteps

Returns a list of Test Steps. Cardinality: targets the full collection or a batch. For a single item by ID, use `getTestStep` instead.

Parametersfieldsincluderevisionmax_itemsprojectIdrequiredpage_size_workItemIdrequiredpage_number_response_format

getUser

Returns the specified User. Cardinality: targets a single item by ID. For the full collection or a batch, use `getUsers` instead.

ParametersfieldsuserIdrequiredincluderevisionresponse_format

getUserGroup

Returns one user group: its ID, name, description, member users, and the global and project roles it grants. Use it to resolve group membership (for example to understand who a group-based assignment or permission covers); for a single user's details use `getUser`.

ParametersfieldsgroupIdrequiredincluderevisionresponse_format

getUsers

Returns a list of Users. Cardinality: targets the full collection or a batch. For a single item by ID, use `getUser` instead. Examples: {"query":"name:Smith","page[size]":20}.

Parameterssortqueryfieldsincluderevisionmax_itemspage_size_page_number_response_format

getWorkItem

Returns the specified Work Item. Cardinality: targets a single item by ID. For the full collection or a batch, use `getWorkItems` instead. Examples: {"projectId":"myproject","workItemId":"WI-123","fields":{"workitems":"id,title,description"}}.

ParametersfieldsincluderevisionprojectIdrequiredworkItemIdrequiredresponse_format

getWorkItemApproval

Returns one user's approval entry on a Work Item, addressed by that user's ID: the approver and their status (`waiting`, `approved`, `disapproved`). Use it to check a single approver's decision; to record or change it use `patchWorkItemApproval`. Cardinality: targets a single item by ID. For the full collection or a batch, use `getWorkItemApprovals` instead.

ParametersfieldsuserIdrequiredincluderevisionprojectIdrequiredworkItemIdrequiredresponse_format

getWorkItemApprovals

Returns the approval entries on one Work Item: each approver (user) and their approval status (`waiting`, `approved`, `disapproved`). Use it to check sign-off progress; to add approvers use `postWorkItemApprovals`, and to record a decision use `patchWorkItemApproval`. Cardinality: targets the full collection or a batch. For a single item by ID, use `getWorkItemApproval` instead.

Parametersfieldsincluderevisionmax_itemsprojectIdrequiredpage_size_workItemIdrequiredpage_number_response_format

getWorkItemAttachment

Returns the specified Work Item Attachment. Cardinality: targets a single item by ID. For the full collection or a batch, use `getWorkItemAttachments` instead.

ParametersfieldsincluderevisionprojectIdrequiredworkItemIdrequiredattachmentIdrequiredresponse_format

getWorkItemAttachmentContent

Downloads the raw file content of one Work Item attachment. Images (PNG, JPEG, GIF, WebP) come back as image content, UTF-8 text files as text, and any other file (PDF, Office, ZIP) as an embedded base64 resource; files over 20 MB are refused. Use this only when you need the file's bytes; for its metadata (fileName, contentType, size, author) call `getWorkItemAttachment`, and to discover attachment IDs call `getWorkItemAttachments`.

ParametersrevisionprojectIdrequiredworkItemIdrequiredattachmentIdrequiredresponse_format

getWorkItemAttachments

Returns a list of Work Item Attachments. Cardinality: targets the full collection or a batch. For a single item by ID, use `getWorkItemAttachment` instead.

Parametersfieldsincluderevisionmax_itemsprojectIdrequiredpage_size_workItemIdrequiredpage_number_response_format

getWorkItemTestParameterDefinition

Returns the specified Test Parameter Definition for the specified Work Item. Cardinality: targets a single item by ID. For the full collection or a batch, use `getWorkItemTestParameterDefinitions` instead.

ParametersfieldsincluderevisionprojectIdrequiredworkItemIdrequiredtestParamIdrequiredresponse_format

getWorkItemTestParameterDefinitions

Returns a list of Test Parameter Definitions for the specified Work Item. Cardinality: targets the full collection or a batch. For a single item by ID, use `getWorkItemTestParameterDefinition` instead.

Parametersfieldsincluderevisionmax_itemsprojectIdrequiredpage_size_workItemIdrequiredpage_number_response_format

getWorkItems

Returns a list of Work Items. Scope: one project (requires a project ID). To act across all projects, use `getAllWorkItems` instead. Cardinality: targets the full collection or a batch. For a single item by ID, use `getWorkItem` instead. For the same collection across projects, use `getAllWorkItems` instead. Examples: {"projectId":"myproject","query":"type:requirement AND status:open","fields":{"workitems":"id,title,status"},"page[size]":25}. Selection: Use getWorkItems when you need matching Work Items in one project; use getAllWorkItems when the search must span every project.

Parameterssortqueryfieldsincluderevisionmax_itemsprojectIdrequiredpage_size_page_number_response_format

getWorkItemsRelationships

Returns the resource identifiers linked from one Work Item through a single named relationship, as JSON:API linkage (`{type, id}` entries) without the related resources' attributes. `relationshipId` is the relationship's name, not an entry ID. Use this to inspect one relationship cheaply; to read the Work Item with its related resources embedded, call its get tool with `include` instead. To change the relationship, use `postWorkItemRelationships` (add), `patchWorkItemRelationships` (replace), or `deleteWorkItemsRelationship` (remove). For Work Item-to-Work Item links with roles, `getLinkedWorkItems` / `getBacklinkedWorkItems` are richer. Examples: {"projectId":"myproject","workItemId":"WI-123","relationshipId":"linkedWorkItems","page[size]":50}.

ParametersfieldsincluderevisionprojectIdrequiredpage_size_workItemIdrequiredpage_number_relationshipIdrequiredresponse_format

getWorkRecord

Returns one work record (time-tracking entry) on a Work Item by its ID: date, time spent, type, comment, and the user who logged it. To remove it use `deleteWorkRecord`. Cardinality: targets a single item by ID. For the full collection or a batch, use `getWorkRecords` instead.

ParametersfieldsincluderevisionprojectIdrequiredworkItemIdrequiredworkRecordIdrequiredresponse_format

getWorkRecords

Returns the work records (time-tracking entries) logged on one Work Item: each with its date, time spent, type, comment, and the user who logged it. Use it to report effort spent on an item; to log time use `postWorkRecords`. Cardinality: targets the full collection or a batch. For a single item by ID, use `getWorkRecord` instead.

Parametersfieldsincluderevisionmax_itemsprojectIdrequiredpage_size_workItemIdrequiredpage_number_response_format

getWorkflowActionsForTestRun

Returns the workflow actions (transitions) possible from one Test Run's current status, each with its action ID, name, target status, whether it is available to the calling user (with an `unavailableReason` if not), and the fields, roles, or signatures it requires. Call it before patchTestRun with `workflowAction` to choose a valid transition; for Work Items use `getWorkflowActionsForWorkItem`.

Parametersrevisionmax_itemsprojectIdrequiredtestRunIdrequiredpage_size_page_number_response_format

getWorkflowActionsForWorkItem

Returns the workflow actions (transitions) possible from one Work Item's current status, each with its action ID, name, target status, whether it is available to the calling user (with an `unavailableReason` if not), and the fields, roles, or signatures it requires. Call it before patchWorkItem with `workflowAction` to choose a valid transition; setting `status` directly bypasses workflow conditions and functions.

Parametersrevisionmax_itemsprojectIdrequiredpage_size_workItemIdrequiredpage_number_response_format

get_document_outline

Get LiveDoc outline

Reads a LiveDoc at the requested revision and returns `{outline}` with each heading’s part ID, title, level, and nested heading path, without rendering body text. Use this to locate a section; call `read_document_section` for its content or `read_document_markdown` for the full document. Requires a project ID, space ID, and document name readable by the signed-in Polarion user.

ParametersspaceIdrequireddocumentrequiredrevisionprojectIdrequired

importExcelTestResults

Imports test results from an Excel file into the specified Test Run and changes its execution data. The file must match the expected Polarion export/import format and the user must have permission to update the run. Use `getExportExcelTests` to create a compatible workbook; use `importWordDocument` for Word-based document import. Effect: triggers a server-side action rather than a plain resource creation — whether repeating it is safe, a no-op, or rejected depends on the specific action; treat it as 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.

Parametersdry_runprojectIdrequiredtestRunIdrequiredrequestBodyrequired

importWordDocument

Imports a Word document as a Polarion LiveDoc, creating or updating document content according to the request options. Requires project and space access plus a valid Word file; use `postDocuments` to create a LiveDoc from JSON:API data or `importExcelTestResults` for test-result spreadsheets. Effect: triggers a server-side action rather than a plain resource creation — whether repeating it is safe, a no-op, or rejected depends on the specific action; treat it as 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.

Parametersdry_runspaceIdrequiredprojectIdrequiredrequestBodyrequired

importXUnitTestResults

Imports XUnit test results. Effect: triggers a server-side action rather than a plain resource creation — whether repeating it is safe, a no-op, or rejected depends on the specific action; treat it as 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.

Parametersdry_runprojectIdrequiredtestRunIdrequiredrequestBodyrequired

lint_query

Lint Lucene Query

Check a Lucene query for unknown work-item fields, unbalanced quotes or parentheses, and suspicious boolean operators. This tool never executes the query.

ParametersqueryrequiredprojectId

markProject

Registers an existing repository folder as a Polarion project (the inverse of `unmarkProject`): `requestBody` names the repository `location`, the new `projectId`, its `trackerPrefix`, and optionally a `templateId`. Runs as an asynchronous job and returns a `jobs` resource; poll `getJob` until it finishes. Use it to re-attach project data that already exists in the repository; to create a brand-new project use `createProject`. Effect: triggers a server-side action rather than a plain resource creation — whether repeating it is safe, a no-op, or rejected depends on the specific action; treat it as 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.

Parametersdry_runrequestBodyrequired

mergeDocumentFromMaster

Merges Master Work Item changes to the specified Branched Document. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runspaceIdrequiredprojectIdrequiredrequestBodydocumentNamerequired

mergeDocumentToMaster

Merges the selected branched LiveDoc content into its master document and returns the merge job/result. Requires a valid branch/master relationship and write access to the master. Use `branchDocument` to create a branch, or `moveDocumentParts` for edits within one document. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runspaceIdrequiredprojectIdrequiredrequestBodydocumentNamerequired

moveDocumentParts

Reorders or relocates parts within a LiveDoc using the requested part IDs and target position. Read current part IDs with `getDocumentParts` first; use `overwriteDocumentParts` only when replacing the document structure rather than moving existing parts. Effect: triggers a server-side action rather than a plain resource creation — whether repeating it is safe, a no-op, or rejected depends on the specific action; treat it as 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.

ParameterspartIdrequireddry_runspaceIdrequiredprojectIdrequiredrequestBodyrequireddocumentNamerequired

moveFromDocument

Removes one Work Item from the Document that currently contains it and returns it to the project's plain Work Item tracker. The Work Item itself is kept with all its fields and links; only its placement in the Document is removed. Use `moveToDocument` for the reverse. Effect: triggers a server-side action rather than a plain resource creation — whether repeating it is safe, a no-op, or rejected depends on the specific action; treat it as 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.

Parametersdry_runprojectIdrequiredworkItemIdrequired

moveProjectAction

Moves project to a different location. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredrequestBodyrequired

moveToDocument

Moves one existing Work Item from the project tracker into a LiveDoc and returns the move result. Requires the Work Item and target document to be writable. Use `moveFromDocument` to return an item to the tracker or `moveWorkItemsToDocument` to move a batch. Effect: triggers a server-side action rather than a plain resource creation — whether repeating it is safe, a no-op, or rejected depends on the specific action; treat it as 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.

Parametersdry_runprojectIdrequiredworkItemIdrequiredrequestBodyrequired

moveWorkItemsToDocument

Moves a batch of existing Work Items from the project tracker into a LiveDoc. Provide the target document and the Work Item IDs in the request body; all items must be accessible and the document writable. Use `moveToDocument` for a single item or `moveFromDocument` to remove one from a document. Effect: triggers a server-side action rather than a plain resource creation — whether repeating it is safe, a no-op, or rejected depends on the specific action; treat it as 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.

Parametersdry_runprojectIdrequiredrequestBodyrequired

overwriteDocumentParts

Replaces the parts of a LiveDoc with the supplied part list. This can remove or replace existing content, so read the current structure with `getDocumentParts` and use `dry_run` before writing. Use `moveDocumentParts` to reposition existing parts while retaining their identities. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runspaceIdrequiredprojectIdrequiredrequestBodyrequireddocumentNamerequired

patchAllWorkItems

Updates a list of Work Items in the Global context. Scope: spans every project (no project filter). To act on a single project, use `patchWorkItems` instead. 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. Examples: {"requestBody":{"data":[{"type":"workitems","id":"myproject/WI-123","attributes":{"status":"inprogress"}}]}}. Selection: Use patchAllWorkItems for a batch spanning projects; use patchWorkItems for a batch in one project and patchWorkItem for one known item.

Parametersdry_runrequestBodyrequiredworkflowAction

patchCollections

Updates one Collection’s attributes from the supplied JSON:API request body. Use `patchCollectionsRelationships` for linkage changes or `postCollections` to create another Collection. 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 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.

Parametersdry_runprojectIdrequiredrequestBodyrequiredcollectionIdrequired

patchCollectionsRelationships

Replaces relationship linkage on one Collection with the supplied relationship data. Read existing links with `getCollectionsRelationship`; use `postCollectionsRelationships` to add links without replacing the full set. Effect: irreversible — data removed or overwritten by this call cannot be recovered through the API. 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.

Parametersdry_runprojectIdrequiredrequestBodyrequiredcollectionIdrequiredrelationshipIdrequired

Version history

1
  1. v1.5.0LatestNov 4, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts