Skip to main content
Glama

update_state

Idempotent

Update an existing state in a project by providing its ID and optional fields such as name, color, and group.

Instructions

Update a state by ID.

Args: project_id: UUID of the project state_id: UUID of the state name: State name color: State color (hex color code) description: State description sequence: State sequence order group: State group (e.g., backlog, unstarted, started, completed, cancelled) is_triage: Whether this is a triage state default: Whether this is the default state external_source: External system source name external_id: External system identifier

Returns: Updated State object

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
colorNo
groupNo
defaultNo
sequenceNo
state_idYes
is_triageNo
project_idYes
descriptionNo
external_idNo
external_sourceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameYes
colorYes
groupNo
defaultNo
projectNo
sequenceNo
is_triageNo
workspaceNo
created_atNo
created_byNo
deleted_atNo
updated_atNo
updated_byNo
descriptionNo
external_idNo
external_sourceNo
Behavior2/5

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

Description adds no behavioral context beyond annotations; annotations already indicate mutation (readOnlyHint=false) and idempotency (idempotentHint=true), but description only restates the parameter list.

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?

Description is concise in the one-liner but includes a verbose parameter list; could be more compact without losing clarity.

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?

Adequate for a simple update operation given output schema exists, but lacks usage context and behavioral details beyond parameters.

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 0%, so description compensates by listing parameters with brief descriptions; provides some added value (e.g., color format, group examples) but mostly mirrors schema types.

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?

Description clearly states the verb 'Update' and the resource 'state by ID', and distinguishes from sibling tools like create_state, delete_state, and list_states.

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 over alternatives; lacks context on when an update is appropriate versus creation or retrieval.

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