Skip to main content
Glama
goto-software

plane-mcp-server

create_label

Add a new label to a project for task categorization. Specify a name, color, and optional parent label to structure your workflow.

Instructions

Create a new label.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
nameYesLabel name
colorNoLabel color (hex color code)
descriptionNoLabel description
parentNoUUID of the parent label (for nested labels)
sort_orderNoSort order for the label
external_sourceNoExternal system source name
external_idNoExternal system identifier

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
created_atNo
updated_atNo
deleted_atNo
nameYes
descriptionNo
colorNo
sort_orderNo
external_sourceNo
external_idNo
created_byNo
updated_byNo
workspaceNo
projectNo
parentNo
Behavior1/5

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

No annotations provided, and description gives no behavioral details: no indication of side effects, permissions needed, or idempotency. The agent cannot infer if creation is reversible or what happens with optional parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short but at the cost of under-specification; it does not earn its place as a useful guide.

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 large number of sibling tools and lack of annotations, the description is far too minimal. An agent cannot determine how labels relate to projects or when to use this tool appropriately.

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 coverage is 100%, so the input schema fully describes parameters. The description adds no additional semantic value beyond what the schema already provides.

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 clearly states the tool creates a new label, but lacks specificity about scope (project-level) and does not distinguish from other create tools like create_cycle or create_state.

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 on when to use create_label versus alternatives, no prerequisites, and no mention of constraints (e.g., duplicate names, required project context).

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