Skip to main content
Glama
goto-software

plane-mcp-server

create_epic

Creates a new epic in Plane. Requires project ID and name; optionally set assignees, priority, dates, and descriptions.

Instructions

Create a new epic.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
nameYesEpic name (required)
assigneesNoList of user IDs to assign to the epic
labelsNoList of label IDs to attach to the epic
pointNoStory point value
description_htmlNoHTML description of the epic
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 epic is a draft
external_sourceNoExternal system source name
external_idNoExternal system identifier
parentNoUUID of the parent epic
stateNoUUID of the state
estimate_pointNoEstimate point value

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
deleted_atNo
created_atNo
updated_atNo
pointNo
nameYes
descriptionNo
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
projectYes
workspaceYes
parentNo
stateNo
estimate_pointNo
typeNo
assigneesNo
labelsNo
Behavior2/5

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states 'Create a new epic,' omitting side effects, required permissions, error conditions, or any impact on the system. For a mutation tool, this is insufficient.

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 extremely short (one sentence) and to the point. While concise, it may be too minimalistic for a tool with many parameters and no annotations. It does not waste words but could benefit from more structure.

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 (17 parameters, no annotations), the description lacks completeness. It does not explain the purpose of an epic in this system, when to create one, or any behavioral context. Although an output schema exists, the description still requires more detail to be fully useful.

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% coverage with descriptions for all 17 parameters. The description does not add any additional meaning beyond what the schema provides. Baseline 3 is appropriate as the schema does the heavy lifting.

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 epic' states the action and resource, but it is essentially a tautology of the tool name. It does not differentiate between this tool and sibling tools like create_cycle or create_initiative, which are similar create operations. A score of 3 is adequate as it is not misleading but lacks context.

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. Sibling tools like update_epic or list_epics exist, but the description offers no criteria for choosing this tool. There is no mention of prerequisites or context for usage.

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