Skip to main content
Glama
goto-software

plane-mcp-server

create_work_item_property

Define new properties for work items in Plane projects by specifying type, display name, and field format.

Instructions

Create a new work item property.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
type_idYesUUID of the work item type
display_nameYesDisplay name for the property
property_typeYesType of property (TEXT, DATETIME, DECIMAL, BOOLEAN, OPTION, RELATION, URL, EMAIL, FILE)
relation_typeNoRelation type (ISSUE, USER) - required for RELATION properties
descriptionNoProperty description
is_requiredNoWhether the property is required
default_valueNoDefault value(s) for the property
settingsNoSettings dictionary - required for TEXT and DATETIME properties For TEXT: {"display_format": "single-line"|"multi-line"|"readonly"} For DATETIME: {"display_format": "MMM dd, yyyy"|"dd/MM/yyyy"|"MM/dd/yyyy"|"yyyy/MM/dd"}
is_activeNoWhether the property is active
is_multiNoWhether the property supports multiple values
validation_rulesNoValidation rules dictionary
external_sourceNoExternal system source name
external_idNoExternal system identifier
optionsNoList of option dictionaries for OPTION properties

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
deleted_atNo
relation_typeNo
created_atNo
updated_atNo
nameNo
display_nameYes
descriptionNo
logo_propsNo
sort_orderNo
property_typeYes
is_requiredNo
default_valueNo
settingsNo
is_activeNo
is_multiNo
validation_rulesNo
external_sourceNo
external_idNo
created_byNo
updated_byNo
workspaceNo
projectNo
issue_typeNo
optionsNo
Behavior1/5

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

No annotations provided; the description only states 'create' without disclosing any behavioral traits such as idempotency, authorization needs, or side effects.

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?

Single sentence with no unnecessary words; maximally concise.

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?

Despite having 15 parameters and an output schema, the description offers no context about what a work item property is, its role, or how it relates to other entities, making it insufficient for complex usage.

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 description coverage is 100%, so the description adds no extra meaning beyond what the schema already provides.

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 'Create a new work item property' uses a specific verb and resource, clearly distinguishing it from sibling tools like 'update_work_item_property' and 'delete_work_item_property'.

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 this tool vs alternatives (e.g., when to create vs update a property, prerequisites like project and type existence).

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