Skip to main content
Glama
kanbanzone

Kanban Zone MCP Server

Official
by kanbanzone

Create a label on a board

kanbanzone_create_label

Create a label on a board using a hex color and description. Optionally set it as the board's default label or specify a sort position.

Instructions

Create a label on a board. Each board can have at most one default label — setting is_default: true automatically clears the flag on any existing default label for the same board.

Args:

  • board (string, required): board publicId.

  • color (string, required): hex color, e.g. "#FF0000".

  • description (string, required): human-readable label text.

  • is_default (boolean, optional): mark this label as the board default.

  • position (number, optional): sort position. Defaults to end of the list.

Examples:

  • "Add an Urgent label to board OeMrbG8g with color #FF0000"

  • "Create a default Backlog label on board OeMrbG8g"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardYes
colorYes
descriptionYes
is_defaultNo
positionNo
Behavior4/5

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

Adds important behavioral detail about default label uniqueness and auto-clearing of existing defaults. Annotations provide readOnlyHint=false, so creation is expected. No further side effects documented.

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?

Well-structured with heading, bullet list, and examples. Every sentence is useful; no wasted words.

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?

Covers inputs and usage well but lacks output description. No output schema exists, so return value (e.g., created label ID) is omitted. Adequate for a basic create tool.

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

Parameters5/5

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

Schema has 0% description coverage; description fully explains each parameter (board, color, description, is_default, position) with defaults and examples, adding significant meaning.

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 'Create a label on a board' with specific action and resource. Distinguishes from sibling tools that create other entities (e.g., cards, checklists).

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?

Description indicates when to use (creating labels) but does not explicitly exclude cases or compare with alternatives like update_label. Basic guidance present.

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/kanbanzone/kanban-zone-mcp-server'

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