Plane MCP Server

Overview Schema Source Related Servers Discussions Admin

Get Work Item

get_work_item

Retrieve a specific work item from a Plane project using its project UUID and work item UUID. Provides the full details needed to inspect or update the item.

Instructions

Fetch a work item by project UUID and work item UUID.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`project_id`	Yes	Project UUID.
`work_item_id`	Yes	Work item UUID. If you only have a human identifier such as "PROJ-123", use `get_work_item_by_identifier` instead.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.1Sep 26, 2026

addedInput schema / properties / project_id / description
```
Added value: +"Project UUID."
```

addedInput schema / properties / work_item_id / description

Added value: +"Work item UUID. If you only have a human identifier such\nas \"PROJ-123\", use `get_work_item_by_identifier` instead."

First observedv0.1.0Sep 26, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and 'Fetch' clearly signals a read-only operation with no mutation. However, it does not disclose error behavior, authentication requirements, or not-found outcomes, which would be useful for a tool with no annotation support.

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?

A single, front-loaded sentence states the action and the two identifying values with no filler or redundant clauses. Every word contributes to the core instruction.

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?

The tool is simple: two required parameters, no nested objects, and an output schema exists. The description plus schema fully cover the main calling scenario and even route the human-identifier case to a sibling tool, leaving little ambiguity for an agent.

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 description coverage is 100%, so the parameters are already fully documented in the input schema. The description repeats the 'UUID' identifiers without adding semantic detail beyond what the schema already provides, meeting the baseline but not exceeding it.

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 names a specific verb ('Fetch') and resource ('work item') and identifies the two required UUIDs, so an agent can understand the core operation. It does not explicitly differentiate from the sibling `get_work_item_by_identifier`, though the parameter description supplies that distinction.

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?

The description implies use when both project and work item UUIDs are available. The `work_item_id` parameter documentation adds an explicit when-not rule by directing agents to `get_work_item_by_identifier` when only a human-readable identifier is present.

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