Skip to main content
Glama
chmald
by chmald

labels

Create, update, delete, assign, or remove color-coded tags on cards and boards to categorize and filter your Kanban workflow.

Instructions

Manage labels on Planka boards and cards. Labels help categorize and filter cards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoBoard ID (for create), Label ID (for update, delete), or Card ID (for addToCard, removeFromCard) (required for: create, update, delete, addToCard, removeFromCard)
dataNoLabel data: { name?: string, color: string, position: number } for create/update, { labelId: string } for addToCard/removeFromCard. Colors: muddy-grey, autumn-leafs, morning-sky, antique-blue, egg-yellow, desert-sand, dark-granite, fresh-salad, lagoon-blue, midnight-blue, light-orange, pumpkin-orange, light-concrete, sunny-grass, navy-blue, lilac-eyes, apricot-red, orange-peel, silver-glint, bright-moss, deep-ocean, summer-sky, berry-red, light-cocoa, grey-stone, tank-green, coral-green, sugar-plum, pink-tulip, shady-rust, wet-rock, wet-moss, turquoise-sea, lavender-fields, piggy-red, light-mud, gun-metal, modern-green, french-coast, sweet-lilac, red-burgundy, pirate-gold (required for: create, update, addToCard, removeFromCard)
actionYesAction to perform: 'create' - Create a label on a board; 'update' - Update a label's name, color, or position; 'delete' - Delete a label from a board; 'addToCard' - Add a label to a card; 'removeFromCard' - Remove a label from a card
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It only states the tool 'manages' labels without revealing side effects, permission requirements, destructive actions (e.g., delete), or any other behavioral traits. The action enum in the schema describes operations, but the description itself adds no 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 extremely concise, consisting of two short sentences. Every word earns its place, with no redundant or irrelevant content, making it easy to parse quickly.

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 tool's multi-action nature and nested data, the schema is thorough, but the description remains minimal. It does not explain the polymorphic use of 'id' (board, label, or card depending on action) nor any permissions or side effects. The schema covers most details, so completeness is adequate but not enriched.

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%, and the action parameter's enum and data object descriptions are quite detailed. The tool description adds no extra meaning beyond the schema, so the baseline score of 3 is appropriate.

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 identifies the tool as managing labels on Planka boards and cards, which clearly distinguishes it from sibling tools like 'boards' or 'cards'. However, the verb 'manage' is generic, and the full range of operations is only revealed via the action parameter in the schema.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. The second sentence ('Labels help categorize and filter cards') hints at a use case but does not explain when to choose labels over other entities like lists or cards, nor does it list exclusions or prerequisites.

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/chmald/planka-mcp'

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