Skip to main content
Glama

retrieve_intake_work_item

Read-only

Retrieve an intake work item by its work item ID to access its details. Use this to get specific information from a Plane project intake.

Instructions

Retrieve an intake work item by work item ID.

Args: workspace_slug: The workspace slug identifier project_id: UUID of the project work_item_id: UUID of the work item (use the issue field from IntakeWorkItem response, not the intake work item ID) params: Optional query parameters as a dictionary (e.g., expand, fields)

Returns: IntakeWorkItem object

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNo
project_idYes
work_item_idYes

Output Schema

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

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

Annotations confirm read-only behavior, which is consistent with 'Retrieve'. Description does not elaborate on side effects or data scope beyond the return type. With readOnlyHint and openWorldHint, additional context missing.

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?

The description is structured as a docstring with clear Args/Returns sections but includes an extra non-existent parameter. It is moderately concise but the error hurts efficiency.

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?

With an output schema, return values are not needed, but the description lacks explanation of what 'intake work item' means versus regular work items. The workspace_slug mismatch indicates incomplete context for a new user.

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

Parameters2/5

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

Schema coverage is 0%, so description must explain parameters. It adds guidance for work_item_id and mentions params, but incorrectly includes workspace_slug which is not in the schema. This error undermines the added value.

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 that it retrieves an intake work item by ID, specifying the action and resource. However, it mentions 'workspace_slug' as an argument that is not present in the input schema, which could cause some confusion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides guidance on using the 'issue field' for work_item_id, but does not explicitly differentiate from sibling tools like 'retrieve_work_item' or 'list_intake_work_items'. The implied usage context is present but not explicit.

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/Bl4nk44/plane-ce-mcp'

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