Skip to main content
Glama

list_work_item_links

Read-only

List a work item's traceability links in either forward (outgoing) or back (incoming) direction, including suspect status.

Instructions

List a work item's outgoing or incoming links.

A single call returns one direction; call twice (direction="forward" then direction="back") when both sides of the traceability graph are needed. Forward links use the /linkedworkitems endpoint and expose the originating role (e.g. parent, relates_to, verifies). Back links fall back to a linkedWorkItems: Lucene query that does not surface the originating role on this server, so role is None for every back-direction item — recover it by calling forward on the source work item.

The suspect flag marks links whose target has changed since the link was last reviewed; it is only meaningful in the forward direction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesPolarion project ID.
work_item_idYesWork Item ID (e.g. 'MCPT-001').
directionNo'forward' (outgoing) or 'back' (incoming); call twice if both needed.forward
page_sizeNoNumber of links per page (1-100, default 100).
page_numberNoPage number to retrieve (1-based, default 1).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
total_countYes
pageYes
page_sizeYes
has_moreNoTrue if more pages follow.
Behavior5/5

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

Discloses that back links fallback to a Lucene query that does not surface the originating role, so role is None. Also explains the 'suspect' flag meaning. This adds substantial behavioral context beyond the readOnlyHint annotation, with no contradiction.

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?

Concise yet comprehensive. The description is a single well-structured paragraph: front-loaded with the main action, followed by specific details. Every sentence adds value with no redundancy.

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 the existence of an output schema (context signal), the description does not need to explain return values. It covers all essential aspects: direction handling, role details, suspect flag, and pagination (via parameters). Complete for a list operation.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds value by explaining the implications of the 'direction' parameter (role behavior, suspect flag) and how to use it, exceeding schema-only information.

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 'List a work item's outgoing or incoming links.' The verb 'list' and resource 'work item links' are specific, and the direction distinction is explicit, differentiating it from sibling tools like create_work_item_links or delete_work_item_links.

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 advises to call twice (forward then back) when both sides are needed. Also explains the behavioral difference between forward and back directions, giving clear guidance on when to use which.

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/devemberx/mcp-server-polarion'

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