Skip to main content
Glama
goto-software

plane-mcp-server

update_project

Update a project's name, description, lead, assignee, and settings by providing its UUID.

Instructions

Update a project by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
nameNoProject name
descriptionNoProject description
project_leadNoUUID of the project lead user
default_assigneeNoUUID of the default assignee user
identifierNoProject identifier
emojiNoEmoji for the project
cover_imageNoCover image URL or asset ID
module_viewNoEnable module view
cycle_viewNoEnable cycle view
issue_views_viewNoEnable issue views view
page_viewNoEnable page view
intake_viewNoEnable intake view
guest_view_all_featuresNoAllow guests to view all features
archive_inNoDays until auto-archive
close_inNoDays until auto-close
timezoneNoProject timezone
external_sourceNoExternal system source name
external_idNoExternal system identifier
is_issue_type_enabledNoEnable issue types
is_time_tracking_enabledNoEnable time tracking
default_stateNoUUID of the default state
estimateNoEstimate configuration

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
total_membersNo
total_cyclesNo
total_modulesNo
is_memberNo
sort_orderNo
member_roleNo
is_deployedNo
cover_image_urlNo
created_atNo
updated_atNo
deleted_atNo
nameYes
descriptionNo
description_textNo
description_htmlNo
networkNo
identifierYes
emojiNo
icon_propNo
module_viewNo
cycle_viewNo
issue_views_viewNo
page_viewNo
intake_viewNo
is_time_tracking_enabledNo
is_issue_type_enabledNo
guest_view_all_featuresNo
cover_imageNo
archive_inNo
close_inNo
logo_propsNo
archived_atNo
timezoneNo
external_sourceNo
external_idNo
created_byNo
updated_byNo
workspaceNo
default_assigneeNo
project_leadNo
cover_image_assetNo
estimateNo
default_stateNo
Behavior2/5

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

The description lacks behavioral details beyond the action. It does not clarify whether updates are partial or full, what permissions are needed, or side effects. No annotations are provided to compensate.

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 a single, front-loaded sentence with no wasted words. It is efficient, though slightly more context on the nature of updates (e.g., partial update) could be added without harming conciseness.

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 complexity of 23 optional parameters and the existence of an output schema, the description is too terse. It does not explain that only provided fields are updated (partial update behavior) or how to handle errors, making it incomplete for effective invocation.

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 baseline is 3. The description adds no extra meaning about parameter relationships or usage 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 'Update a project by ID' clearly states the action (update) and resource (project) with the identification method. It effectively distinguishes from sibling tools like update_project_features, create_project, and delete_project.

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?

The description provides no guidance on when to use this tool versus alternatives such as update_project_features (which modifies view settings) or when to avoid it. No prerequisites or exclusions are mentioned.

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