Skip to main content
Glama
goto-software

plane-mcp-server

update_state

Modify a state in a project by providing its ID and updating fields like name, color, description, sequence, or group.

Instructions

Update a state by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
state_idYesUUID of the state
nameNoState name
colorNoState color (hex color code)
descriptionNoState description
sequenceNoState sequence order
groupNoState group (e.g., backlog, unstarted, started, completed, cancelled)
is_triageNoWhether this is a triage state
defaultNoWhether this is the default state
external_sourceNoExternal system source name
external_idNoExternal system identifier

Output Schema

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Update' implies mutation, but it does not specify side effects, required permissions, idempotency, or whether it supports partial updates despite many optional 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?

The description is a single sentence, which is concise but lacks structure. It does not provide any additional context or organization that would help the agent quickly grasp the tool's purpose.

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?

Given the comprehensive schema and presence of an output schema, the description is minimally adequate. However, it lacks contextual completeness regarding usage, behavior, and relationship to sibling tools, which is a gap.

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 all parameters are documented in the schema. The tool description adds no additional meaning beyond what is already in the schema, which is adequate but not enhanced.

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 'Update a state by ID' clearly states the action (update), resource (state), and identifier (by ID). It is specific and avoids ambiguity, though it does not differentiate from other update tools among 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_state or delete_state. The description lacks context about prerequisites or scenarios for updating a state.

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