Skip to main content
Glama
goto-software

plane-mcp-server

create_work_item

Add a new task to a project with assignees, labels, priority, dates, and other attributes.

Instructions

Create a new work item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
nameYesWork item name (required)
assigneesNoList of user IDs to assign to the work item
labelsNoList of label IDs to attach to the work item
type_idNoUUID of the work item type
pointNoStory point value
description_htmlNoHTML description of the work item
description_strippedNoPlain text description (stripped of HTML)
priorityNoPriority level (urgent, high, medium, low, none)
start_dateNoStart date (ISO 8601 format)
target_dateNoTarget/end date (ISO 8601 format)
sort_orderNoSort order value
is_draftNoWhether the work item is a draft
external_sourceNoExternal system source name
external_idNoExternal system identifier
parentNoUUID of the parent work item
stateNoUUID of the state
estimate_pointNoEstimate point value
typeNoWork item type identifier

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
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
Behavior1/5

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

Despite no annotations, the description fails to disclose any behavioral traits such as side effects, return value, idempotency, or required permissions. It does not mention the output schema existence or what the tool does beyond creation.

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 concise at five words, but it adds little value. It is front-loaded but lacks substantive information to earn its place; it could be replaced by the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (19 parameters, many siblings, no annotations, yet an output schema exists), the description is severely incomplete. It does not explain what a work item is, how it relates to projects, or how it differs from other create tools.

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?

The input schema has 100% description coverage, so the schema already documents all 19 parameters. The description adds no additional meaning or context beyond the schema's own descriptions. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a new work item' restates the tool name with minimal additional context. It specifies the verb and resource, but it's nearly tautological, and doesn't clarify what distinguishes a work item from other entities like episodes or cycles among siblings.

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 is provided on when to use this tool versus alternatives like 'create_initiative' or 'create_intake_work_item'. The description lacks any context about prerequisites, typical use cases, 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