Polarion MCP

Overview Schema Source Related Servers Discussions Admin

list_work_items

Read-only

Search and filter work items in a Polarion project using Lucene or SQL queries to locate requirements, test cases, and defects.

Instructions

List / search work items in a project.

Leading Lucene wildcards are rejected; module and body text are NOT Lucene-indexed — scope by document via SQL:(...) or read_document_parts, never a Lucene module term. For SQL:(...), call get_sql_query_recipes first and adapt a recipe — never hand-write SQL. For one known id, use get_work_item instead of scanning.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	No	Optional Lucene filter (e.g. 'type:requirement', 'title:SRS*') OR a 'SQL:(...)' prefix for native SQL.
`page_size`	No
`project_id`	Yes	Polarion project ID.
`page_number`	No

Output Schema

TableJSON 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.

Changed3 schema fields changedv2.0.0Jul 22, 2026

changedOutput schema / properties / items / items / description

Previous value: -"Compact work-item representation for list and search results."New value: +"Compact work-item view for list + search results."

removedOutput schema / properties / items / items / properties / assignee_ids

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

addedOutput schema / properties / items / items / properties / author_name
```
Added value: +{
+  "default": "",
+  "type": "string"
+}
```

Changed13 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 work items per page (1-100, default 100)."

removedOutput schema / properties / has_more / description
```
Removed value: -"True if more pages follow."
```

changedOutput schema / properties / items / items / description

Previous value: -"Compact work-item representation for list and search results.\n\n``space_id`` + ``document_name`` together address the containing\ndocument (both empty when the work item is free-floating); pass them\nto ``get_document`` / ``read_document_parts``."New value: +"Compact work-item representation for list and search results."

removedOutput schema / properties / items / items / properties / assignee_ids / description
```
Removed value: -"Short user IDs of assignees; empty list when unassigned."
```
removedOutput schema / properties / items / items / properties / document_name / description
```
Removed value: -"Containing document name; empty when free-floating."
```
removedOutput schema / properties / items / items / properties / id / description
```
Removed value: -"Work Item ID (e.g. 'MCPT-001')."
```
removedOutput schema / properties / items / items / properties / priority / description
```
Removed value: -"Priority value as a string (e.g. '90.0'); empty when unset."
```
removedOutput schema / properties / items / items / properties / space_id / description
```
Removed value: -"Containing document's space; empty when free-floating."
```
removedOutput schema / properties / items / items / properties / status / description
```
Removed value: -"Workflow status (e.g. 'draft', 'approved')."
```
removedOutput schema / properties / items / items / properties / title / description
```
Removed value: -"Work Item title."
```
removedOutput schema / properties / items / items / properties / type / description
```
Removed value: -"Work Item type (e.g. 'requirement', 'testCase')."
```
removedOutput schema / properties / items / items / properties / updated / description
```
Removed value: -"ISO-8601 last-modified timestamp; empty when unreported."
```

First observedv0.9.0May 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Discloses that leading wildcards are rejected, module and body text are not Lucene-indexed, and advises using SQL via get_sql_query_recipes. Annotations already state readOnlyHint=true, consistent.

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

Conciseness4/5

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

Two sentences pack essential information, but second sentence is dense with multiple pieces of guidance. Still efficient and front-loaded.

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

Completeness5/5

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

Given output schema exists, description covers behavior, limitations, and alternatives comprehensively. No gaps apparent.

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

Parameters4/5

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

Adds context beyond schema for query parameter (e.g., module/body text not indexed) but schema already describes query types. Other parameters not elaborated, but schema coverage is 50%.

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?

Clearly states the tool lists/searches work items in a project, distinguishes from get_work_item for single item and mentions read_document_parts as alternative for scope.

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

Usage Guidelines5/5

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

Explicitly says when not to use (e.g., for one known id) and provides guidance on query types (avoid leading wildcards, use get_sql_query_recipes before hand-writing SQL).

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

Deploy Server