Skip to main content
Glama
goto-software

plane-mcp-server

retrieve_work_item_by_identifier

Retrieve a work item by project identifier and issue sequence number.

Instructions

Retrieve a work item by project identifier and issue sequence number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_identifierYesProject identifier string (e.g., "MP" for "My Project")
issue_identifierYesIssue sequence number (e.g., 1, 2, 3)
expandNoComma-separated fields to expand (e.g., "assignees,labels,state")
fieldsNoComma-separated list of 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 carries full burden for behavioral transparency, but it only re-states the action without disclosing traits like read-only nature, error behavior, or performance implications.

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?

The description is a single sentence that immediately conveys the core action and required identifiers, with no extraneous words.

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?

Given the presence of an output schema and well-documented parameters, the description is mostly complete, though it could mention that it returns a single work item exactly matching the identifiers.

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% with detailed parameter descriptions; the description adds minimal value by naming the two key parameters but does not enhance understanding beyond the schema.

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?

The description clearly states the verb 'Retrieve' and the resource 'work item', and identifies the required identifiers (project identifier and issue sequence number), distinguishing it from similar retrieve tools like retrieve_work_item.

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?

The description provides no guidance on when to use this tool over alternatives (e.g., retrieve_work_item or search_work_items) and does not mention any prerequisites or context for usage.

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