Skip to main content
Glama
phillipboesger

Polarion MCP Server

deleteExternallyLinkedWorkItems

Delete externally linked work items from a work item in a Polarion project. Requires project ID, work item ID, and an array of linked item IDs in the request body.

Instructions

Deletes a list of Externally Linked Work Items.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesThe Project ID.
workItemIdYesThe Work Item ID.
requestBodyYesThe Work Item(s) body.
Behavior2/5

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

No annotations provided, so the description must disclose behavioral traits. It does not mention whether the operation is destructive, requires specific permissions, or what happens to related data. The description only states the action without any side effects or constraints.

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

Conciseness3/5

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

The description is a single sentence, which is concise but under-informative. It could include more detail without becoming verbose, such as clarifying the parameter relationship or noting that it deletes multiple items.

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

Completeness2/5

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

Given the complexity of the input schema (nested objects, multiple required parameters) and lack of output schema, the description is insufficient. It does not explain how to specify the list of items, the role of workItemId, or the expected behavior, leaving the agent with gaps.

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 100%, so the parameter names and types are documented. However, the description adds no meaning beyond the schema, especially lacking explanation of how 'workItemId' relates to the 'requestBody' data array. The nested structure and the 'workItemId' field's purpose are left unclear.

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

Purpose3/5

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

The description states it deletes a list of Externally Linked Work Items, which is clear at a high level. However, the tool name 'deleteExternallyLinkedWorkItems' contrasts with the sibling 'deleteExternallyLinkedWorkItem', and the description does not clarify how 'list' differs from singular deletion. The verb and resource are present but the scope is ambiguous.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus siblings like deleteLinkedWorkItems, deleteWorkItems, or deleteExternallyLinkedWorkItem. The description lacks any context for selection, prerequisites, or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/phillipboesger/polarion-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server