Polarion MCP

Overview Schema Source Related Servers Discussions Admin

list_documents

Read-only

List all documents in a Polarion project, returning IDs, names, type, status, and metadata to identify and reference them for further actions.

Instructions

List a project's documents.

Returns space_id + document_name — the inputs to every other document tool — plus type, status, updated, and creator/editor display names. Use get_document for author/editor ids. Discovery scan cached 60s.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>"
    },
    "name": "list_documents"
  }
}

Input Schema

Name	Required	Description
`page_size`	No
`project_id`	Yes	Polarion project ID.
`page_number`	No

Output Schema

Name	Required	Description	Default
`page`	Yes
`items`	Yes
`has_more`	No
`page_size`	Yes
`total_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.0Jul 22, 2026
Removedv2.0.0Jul 22, 2026
Changed4 schema fields changedv1.4.0Jun 26, 2026
- addedOutput schema / properties / items / items / properties / author
```
Added value: +{
+  "default": "",
+  "type": "string"
+}
```
- addedOutput schema / properties / items / items / properties / last_updated_by
```
Added value: +{
+  "default": "",
+  "type": "string"
+}
```
- addedOutput schema / properties / items / items / properties / status
```
Added value: +{
+  "default": "",
+  "type": "string"
+}
```
- addedOutput schema / properties / items / items / properties / updated
```
Added value: +{
+  "default": "",
+  "type": "string"
+}
```
Changed1 schema field changedv1.2.0Jun 10, 2026
- addedOutput schema / properties / items / items / properties / type
```
Added value: +{
+  "default": "",
+  "type": "string"
+}
```
Changed5 schema fields changedv1.1.0Jun 9, 2026
- removedInput schema / properties / page_number / description
```
Removed value: -"Page number to retrieve (1-based, default 1)."
```
- removedInput schema / properties / page_size / description
```
Removed value: -"Number of documents per page (1-100, default 100)."
```
- removedOutput schema / properties / has_more / description
```
Removed value: -"True if more pages follow."
```
- removedOutput schema / properties / items / items / properties / document_name / description
```
Removed value: -"Document name within the space."
```
- removedOutput schema / properties / items / items / properties / space_id / description
```
Removed value: -"Space containing the document (e.g. '_default')."
```
First observedv0.9.0May 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Description adds caching behavior (60s) beyond readOnlyHint annotation. Also lists returned fields, providing transparency on output. No contradiction with annotations.

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

Conciseness5/5

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

Two concise sentences with front-loaded purpose. No redundancy; every sentence adds value.

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

Completeness4/5

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

Given output schema exists to document return values, description completes the picture with caching and tool differentiation. Missing parameter details slightly reduce completeness.

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

Parameters2/5

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

Schema coverage is only 33% (project_id described). Description implies project_id needed but does not explain page_size or page_number. With low coverage, description should compensate, but it falls short.

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

Purpose5/5

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

Clear verb-resource pair: 'List a project's documents.' Specifies returned fields (space_id, document_name, etc.) and explicitly distinguishes sibling tool get_document by stating when to use it for author/editor ids.

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

Usage Guidelines4/5

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

Provides guidance to use get_document for more detail, implying this tool is for summary listing. Also mentions 60-second cache, but lacks explicit when-not-to-use or alternatives beyond get_document.

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

Deploy Server