Skip to main content
Glama

create_work_item

Create a new work item in a project. Specify name, assignees, priority, dates, and more to define tasks or issues.

Instructions

Create a new work item.

Args: project_id: UUID of the project name: Work item name (required) assignees: List of user IDs to assign to the work item labels: List of label IDs to attach to the work item type_id: UUID of the work item type point: Story point value description_html: HTML description of the work item description_stripped: Plain text description. Convenience only - it is wrapped into HTML and stored as description_html (Plane derives description_stripped server-side). Ignored if description_html is set. priority: Priority level (urgent, high, medium, low, none) start_date: Start date (ISO 8601 format) target_date: Target/end date (ISO 8601 format) sort_order: Sort order value is_draft: Whether the work item is a draft external_source: External system source name external_id: External system identifier parent: UUID of the parent work item state: UUID of the state estimate_point: Estimate point value type: Work item type identifier

Returns: Created WorkItem object

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
typeNo
pointNo
stateNo
labelsNo
parentNo
type_idNo
is_draftNo
priorityNo
assigneesNo
project_idYes
sort_orderNo
start_dateNo
external_idNo
target_dateNo
estimate_pointNo
external_sourceNo
description_htmlNo
description_strippedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
typeNo
pointNo
stateNo
parentNo
projectNo
type_idNo
is_draftNo
priorityNo
workspaceNo
created_atNo
created_byNo
deleted_atNo
sort_orderNo
start_dateNo
updated_atNo
updated_byNo
archived_atNo
external_idNo
sequence_idNo
target_dateNo
completed_atNo
estimate_pointNo
external_sourceNo
description_htmlNo
description_binaryNo
description_strippedNo
Behavior2/5

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

Annotations already indicate non-read-only (writes) and non-destructive. The description adds no behavioral context beyond stating it creates a work item. No mention of permissions, side effects, or rate limits. With annotations present, the description falls short of adding significant behavioral insight.

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 well-structured with an Args block and clear line-by-line parameter definitions. It is front-loaded with the purpose. While lengthy due to many parameters, every sentence adds information, earning its place.

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

Completeness4/5

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

Given the complexity (19 parameters, output schema exists), the description adequately explains parameters and return type. However, it does not differentiate from other creation tools (e.g., create_intake_work_item) or mention when to use this specific tool, leaving a minor gap in completeness.

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

Parameters5/5

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

Schema description coverage is 0%, but the description provides extensive explanations for each parameter, including types, requiredness, and special behavior (e.g., description_stripped being ignored if description_html is set). This adds substantial value beyond the bare schema.

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 starts with 'Create a new work item,' which clearly states the verb and resource. It distinguishes itself from siblings like update_work_item and delete_work_item by focusing on creation, and the parameter list clarifies the scope.

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 does not explicitly state when to use this tool versus alternatives (e.g., create_intake_work_item), nor does it provide exclusions or prerequisites. Usage is implied by the purpose but lacks explicit guidance.

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