Skip to main content
Glama
goto-software

plane-mcp-server

update_intake_work_item

Update an existing intake work item by providing its project, work item ID, and modified data dictionary.

Instructions

Update 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)
dataYesUpdated intake work item data as a dictionary

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?

No annotations are provided, so the description must disclose behavioral traits. It merely says 'Update', which is obvious from the name, and does not mention permissions, side effects, or data mutation details. This is insufficient for a write operation.

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 sentence of 8 words, which is concise and front-loaded. However, it could be expanded slightly 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?

Given the tool is a mutation with an output schema, the description does not explain update semantics (full replace vs merge), idempotency, or validation rules. The flexible 'data' object (additionalProperties true) requires more context for correct usage.

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 baseline is 3. The description adds no additional meaning beyond the schema. The schema itself provides clear descriptions for each parameter.

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 verb 'Update' and resource 'intake work item' with method 'by work item ID'. It distinguishes itself from sibling create/delete tools, but not from 'update_work_item' (which updates a regular 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 usage guidance is provided. The description does not specify when to use this tool instead of alternatives like update_work_item, nor does it mention any prerequisites or exclusions.

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