Skip to main content
Glama
goto-software

plane-mcp-server

retrieve_intake_work_item

Retrieve a specific intake work item by its ID for project management tasks. Use this to fetch details of a work item within a project.

Instructions

Retrieve an intake work item by work item ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
work_item_idYesUUID of the work item (use the issue field from IntakeWorkItem response, not the intake work item ID)
paramsNoOptional query parameters as a dictionary (e.g., expand, fields)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
issue_detailNo
inboxNo
created_atNo
updated_atNo
deleted_atNo
statusNo
snoozed_tillNo
sourceNo
source_emailNo
external_sourceNo
external_idNo
extraNo
created_byNo
updated_byNo
projectNo
workspaceNo
intakeNo
issueNo
duplicate_toNo
Behavior2/5

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

With no annotations, description carries full burden but only states 'retrieve' – no disclosure of side effects, error behavior, or access requirements.

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?

Single sentence is concise but omits critical parameter context (project_id), making it too terse to be fully effective.

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 schema covering parameters, description misses required project_id and special work_item_id note, and provides no usage context for the optional params. Output schema exists but insufficient to compensate.

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 descriptions; tool description adds no extra meaning, baseline 3 applies.

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?

Description states verb 'retrieve' and resource 'intake work item' with key 'work item ID', but fails to mention the required project_id parameter, and does not differentiate from sibling 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?

No guidance on when to use vs alternatives; no exclusions or context provided beyond implied retrieval by ID.

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