Skip to main content
Glama
goto-software

plane-mcp-server

retrieve_work_item

Retrieve a specific work item by providing its project and work item IDs, with optional field expansion and filtering.

Instructions

Retrieve a work item by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
work_item_idYesUUID of the work item
expandNoComma-separated fields to expand (e.g., "assignees,labels,state")
fieldsNoComma-separated fields to include in response
external_idNoExternal system identifier for filtering
external_sourceNoExternal system source name for filtering
order_byNoField to order results by (typically not used for single item retrieval)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
assigneesYes
labelsYes
type_idNo
created_atNo
updated_atNo
deleted_atNo
pointNo
nameYes
description_htmlNo
description_strippedNo
description_binaryNo
priorityNo
start_dateNo
target_dateNo
sequence_idNo
sort_orderNo
completed_atNo
archived_atNo
is_draftNo
external_sourceNo
external_idNo
created_byNo
updated_byNo
projectNo
workspaceNo
parentNo
stateNo
estimate_pointNo
typeNo
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only says 'by ID'. Lacks information on permissions, rate limits, response structure, or whether it retrieves by internal UUID vs external identifier.

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?

The description is a single concise sentence with no fluff. It's front-loaded and efficient, but could be expanded with key details without losing conciseness.

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?

Despite having an output schema (not shown), the description lacks context: it doesn't mention that it returns a single work item object, nor does it explain optional parameters like expand or fields. Given the complexity (7 parameters, no annotations), the description is insufficient.

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

Parameters3/5

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

Schema coverage is 100% and each parameter already has a description. The tool description adds no additional meaning beyond what's in the schema, so baseline 3 is appropriate.

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

Purpose4/5

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

The description clearly states the action (Retrieve) and resource (work item) using ID. However, it does not differentiate from sibling retrieve tools like retrieve_work_item_by_identifier.

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 alternatives such as retrieve_work_item_by_identifier or list_work_items. The description is too brief to provide usage context.

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/goto-software/plane-mcp-server'

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