Skip to main content
Glama
goto-software

plane-mcp-server

update_work_item_property

Update a work item property's attributes like display name, type, or settings using its unique IDs for project, type, and property.

Instructions

Update a work item property by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
type_idYesUUID of the work item type
work_item_property_idYesUUID of the property
display_nameNoDisplay name for the property
property_typeNoType of property (TEXT, DATETIME, DECIMAL, BOOLEAN, OPTION, RELATION, URL, EMAIL, FILE)
relation_typeNoRelation type (ISSUE, USER) - required when updating to RELATION
descriptionNoProperty description
is_requiredNoWhether the property is required
default_valueNoDefault value(s) for the property
settingsNoSettings dictionary - required when updating to TEXT or DATETIME 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

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
Behavior2/5

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

Annotations are absent, so the description carries the full burden. It only states it updates, but does not disclose any behavioral traits like required permissions, potential side effects, or error conditions.

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 very short (6 words), but it lacks necessary information for a tool with 15 parameters. Conciseness is good, but structure is minimal.

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 (15 parameters, many conditional), the description is too brief. It does not mention required parameters or provide any context beyond the basic action.

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 baseline is 3. The description adds no additional meaning beyond what the schema already provides for parameters.

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 the verb 'Update' and the resource 'work item property', and specifies 'by ID', which distinguishes it from create/delete siblings.

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 versus alternatives like create_work_item_property or delete_work_item_property. The context does not provide any usage hints.

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