Skip to main content
Glama

update_label

Idempotent

Update an existing label's name, color, description, parent, sort order, or external references by providing its project and label IDs.

Instructions

Update a label by ID.

Args: project_id: UUID of the project label_id: UUID of the label name: Label name color: Label color (hex color code) description: Label description parent: UUID of the parent label (for nested labels) sort_order: Sort order for the label external_source: External system source name external_id: External system identifier

Returns: Updated Label object

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
colorNo
parentNo
label_idYes
project_idYes
sort_orderNo
descriptionNo
external_idNo
external_sourceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameYes
colorNo
parentNo
projectNo
workspaceNo
created_atNo
created_byNo
deleted_atNo
sort_orderNo
updated_atNo
updated_byNo
descriptionNo
external_idNo
external_sourceNo
Behavior3/5

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

Annotations already indicate readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds no extra behavioral context (e.g., side effects on label relationships, permissions needed). With annotations, the bar is lower, but additional detail like 'only updates provided fields' would improve transparency.

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 concise and well-structured: a one-line purpose, followed by a clear list of parameters with descriptions, ending with 'Returns: Updated Label object'. No extraneous information.

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

Completeness4/5

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

Given 9 parameters (2 required) and an existing output schema, the description covers all parameters and indicates the return type. Could mention that only non-null fields are updated (since defaults are null), but overall complete for an update operation.

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%, but the description provides brief explanations for each of the 9 parameters in the Args block. This adds meaning beyond the schema's type-only definitions, guiding the user on what each parameter represents.

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 starts with 'Update a label by ID' - a clear verb+resource combination. The tool name and description align. It distinguishes from sibling tools like create_label, delete_label, retrieve_label, list_labels.

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?

No explicit guidance on when to use this tool vs alternatives like create_label or delete_label. The context of 'update' implies it's for modifying existing labels, but no when-not-to-use or prerequisites 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