Skip to main content
Glama

update_project

Idempotent

Update a project's settings and metadata, including name, description, visibility, and feature toggles, by specifying the project ID.

Instructions

Update a project by ID.

Args: workspace_slug: The workspace slug identifier project_id: UUID of the project name: Project name description: Project description project_lead: UUID of the project lead user default_assignee: UUID of the default assignee user identifier: Project identifier emoji: Emoji for the project cover_image: Cover image URL or asset ID network: Project visibility (0=secret, 2=public) module_view: Enable module view cycle_view: Enable cycle view issue_views_view: Enable issue views view page_view: Enable page view intake_view: Enable intake view guest_view_all_features: Allow guests to view all features archive_in: Days until auto-archive close_in: Days until auto-close timezone: Project timezone external_source: External system source name external_id: External system identifier is_issue_type_enabled: Enable issue types is_time_tracking_enabled: Enable time tracking default_state: UUID of the default state estimate: Estimate configuration

Returns: Updated Project object

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
emojiNo
networkNo
close_inNo
estimateNo
timezoneNo
page_viewNo
archive_inNo
cycle_viewNo
identifierNo
project_idYes
cover_imageNo
descriptionNo
external_idNo
intake_viewNo
module_viewNo
project_leadNo
default_stateNo
external_sourceNo
default_assigneeNo
issue_views_viewNo
is_issue_type_enabledNo
guest_view_all_featuresNo
is_time_tracking_enabledNo

Output Schema

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

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

Annotations already indicate non-destructive, idempotent, non-read-only. Description adds return type but no extra behavioral details like default behavior for omitted parameters.

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?

Structured as a docstring with purpose first, but parameter list is lengthy. No unnecessary wording, but could be more concise by omitting obvious parameter names.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return info is covered. Parameter documentation is adequate for a simple update, but lacks context on usage scenarios or parameter interactions.

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?

22 parameters described with one-line explanations, adding meaning beyond schema types. However, many descriptions are minimal and schema coverage is 0%, so description partially compensates.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Update a project by ID' and lists parameters. It distinguishes from create/delete, but not from update_project_features, a sibling that might overlap.

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 vs alternatives like update_project_features. No when-not-to-use or exclusion criteria 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/Bl4nk44/plane-ce-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server