Done Bear MCP

Create Label

label_create

Create a new label in the workspace and return its id. Only creates the label: to put it on a task, pass it to task_add labels or task_edit add_labels afterwards (both take the title). Titles are not unique, so a second call with the same title makes a duplicate — check the labels get_context returns first, and reuse one that already exists.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	Label title
`context`	Yes	Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
`workspace`	No	Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices
`idempotency_key`	No	Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`ok`	Yes
`title`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

changedInput schema / properties / workspace / description

Previous value: -"Workspace id, slug, or name"New value: +"Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices"

First observedSep 1, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations declare it is a non-read-only mutator that is not destructive; the description adds a genuinely useful behavioral trait — titles are not unique, so repeated calls duplicate rather than no-op. It does not mention the idempotency_key retry-safety behavior, though the schema documents that parameter.

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?

Three sentences, each earning its place: scope, follow-up routing, and the duplicate-avoidance warning. The creation semantics are front-loaded before the caveat.

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

Completeness5/5

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

An output schema exists, so the description needn't detail return values, and it still notes the id is returned. For a simple create tool it covers scope, sibling routing, and the main failure mode (duplicates) completely.

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 coverage is 100%, so the baseline is 3, but the description adds cross-tool semantics for `title`: it is the same value passed to task_add `labels` and task_edit `add_labels`, and it is non-unique. It does not elaborate on `workspace` or `idempotency_key`, which the schema already covers.

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?

States a specific verb+resource ('Create a new label in the workspace') and even names the return value (its id). It explicitly distinguishes itself from sibling tools task_add and task_edit, which it says must be used afterwards to attach the label.

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

Usage Guidelines5/5

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

Gives explicit when-to-use routing: this tool only creates, and attaching requires task_add `labels` or task_edit `add_labels`. It also prescribes a check-first workflow (consult get_context's labels and reuse an existing one) before calling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Done Bear MCP tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?