Plane MCP

create_work_item

Creates a new work item in Plane with optional priority, state, assignees, labels, dates, and estimates. Only a name is required to start.

Instructions

Create a work item. Only name is required.

priority: none|urgent|high|medium|low
state: a STATE UUID (use list_states to find it)
assignees/labels: lists of UUIDs (use list_members / list_labels)
dates: 'YYYY-MM-DD'

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "create_work_item"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`state`	No
`labels`	No
`parent`	No
`priority`	No
`assignees`	No
`project_id`	No
`start_date`	No
`target_date`	No
`estimate_point`	No
`description_html`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 6, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Create a work item' which implies a mutating action, but it does not mention side effects, return behavior, default state, idempotency, or any other behavioral traits. This is a significant gap for a creation tool.

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 exceptionally concise, using bullet points to convey parameter formats and requirements. The most critical fact ('Only `name` is required') is front-loaded. Every line provides actionable information without redundancy.

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's complexity (11 parameters, no annotations, no schema descriptions), the description is under-specified. It explains formats for only some parameters and omits context for others, such as what `parent` or `estimate_point` mean. While an output schema exists (so return values need not be described), the description is insufficient to fully guide correct usage for a tool with this many parameters.

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 schema has 0% description coverage, so the description must compensate. It adds meaningful details for priority (explicit enum values), state (UUID via list_states), assignees/labels (lists of UUIDs), and dates (format). However, it leaves several parameters undocumented in both schema and description: parent, project_id, estimate_point, and description_html. The coverage is partial, not complete.

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 'Create a work item' with a specific verb and resource, distinguishing it from siblings like update_work_item, list_work_items, and get_work_item. The purpose is unambiguous.

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?

The description provides some usage context by noting 'Only `name` is required' and pointing to helper tools (list_states, list_members, list_labels) for obtaining UUIDs. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.