Skip to main content
Glama

create_state

Create a new state to define custom workflow stages in a Plane project. Specify name, color, and group to organize work items.

Instructions

Create a new state.

Args: project_id: UUID of the project 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: Created State object

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
colorYes
groupNo
defaultNo
sequenceNo
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?

With no annotations, the description carries full burden for behavioral disclosure. It only says 'Create a new state' and lists parameters, but does not clarify side effects, permissions, uniqueness constraints, default behavior, or error conditions. This is insufficient for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a concise, well-structured docstring with a clear opening statement followed by a parameter list. No unnecessary words or repetition; every line contributes to understanding the tool.

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?

The tool has 10 parameters, no annotations, and an output schema. The description documents all parameters and return value, but lacks usage context, prerequisites, and behavioral details. Given the complexity, it is adequate but not comprehensive, especially since the agent might need to know when creation is appropriate versus updating an existing state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It lists all 10 parameters with brief explanations, including useful context for 'group' (e.g., backlog, unstarted) and 'color' (hex code). However, some explanations are tautological (e.g., 'description: State description'), which prevents a perfect score.

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 'Create a new state.' with a specific verb and resource. It distinguishes from sibling tools like list_states, retrieve_state, update_state, and delete_state without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through the verb 'create' but does not explicitly state when to use this tool versus alternatives. No exclusions or alternative tool references are mentioned, leaving the agent to infer from the tool name and sibling list.

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/leigangzhang/plane-mcp-server-adapter'

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