Done Bear

Edit Task

task_edit

Idempotent

Update fields on one task (task) or on several at once (tasks, max 50). Only the provided fields are changed; omitted fields are left untouched. To remove a value, list the field in clear (e.g. clear: ["deadline"]). Notes replace the existing notes (no append). assignee assigns the task; clear it to unassign. add_labels and remove_labels change which labels are on it. Editing several tasks applies the same changes to every one of them and cannot be undone in one call, so confirm the list with the user first. For status changes use task_done, task_reopen or task_archive, and for checklist items use checklist; this tool does not change either.

Input Schema

TableJSON Schema

Name	Required	Description
`task`	No	Workspace-scoped task number, encoded as a string
`team`	No	Team id, key, or name
`when`	No	Move to a different GTD view
`clear`	No	Fields to remove a value from, e.g. ["deadline"]. Use this rather than sending an empty string.
`notes`	No	New description/notes (replaces existing)
`tasks`	No	Several workspace-scoped task numbers (max 50), instead of `task`. Confirm the list with the user first: one call changes every task in it.
`title`	No	New 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."
`project`	No	Project id, key, or name
`assignee`	No	Assign to a member (user id, name, or email)
`deadline`	No	Set due date (YYYY-MM-DD)
`timezone`	No	IANA timezone used to resolve "today" for views and scheduling (e.g. Australia/Melbourne). Defaults to UTC, which misclassifies Today/Upcoming for users in other timezones, so always pass the user's timezone when known.
`workspace`	No	Workspace id, slug, or name
`add_labels`	No	Labels to attach (each a label id, title, or id prefix). The label has to exist already — create one with label_create
`remove_labels`	No	Labels to detach (each a label id, title, or id prefix)

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`count`	Yes
`tasks`	Yes	Every task the call changed, in the order it was given
`action`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedSep 4, 2026

addedInput schema / properties / add_labels

Added value: +{
+  "description": "Labels to attach (each a label id, title, or id prefix). The label has to exist already — create one with label_create",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / remove_labels

Added value: +{
+  "description": "Labels to detach (each a label id, title, or id prefix)",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / tasks

Added value: +{
+  "description": "Several workspace-scoped task numbers (max 50), instead of `task`. Confirm the list with the user first: one call changes every task in it.",
+  "items": {
+    "description": "Workspace-scoped task number, encoded as a string",
+    "pattern": "^[1-9]\\d*$",
+    "type": "string"
+  },
+  "maxItems": 50,
+  "minItems": 1,
+  "type": "array"
+}

changedInput schema / required

Previous value: -[
-  "task",
-  "context"
-]New value: +[
+  "context"
+]

addedOutput schema / properties / count

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

removedOutput schema / properties / id

Removed value: -{
-  "type": "string"
-}

removedOutput schema / properties / number

Removed value: -{
-  "exclusiveMinimum": 0,
-  "maximum": 9007199254740991,
-  "type": "integer"
-}

addedOutput schema / properties / tasks

Added value: +{
+  "description": "Every task the call changed, in the order it was given",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "number": {
+        "exclusiveMinimum": 0,
+        "maximum": 9007199254740991,
+        "type": "integer"
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "number",
+      "title"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "action",
-  "id",
-  "number",
-  "ok"
-]New value: +[
+  "action",
+  "count",
+  "ok",
+  "tasks"
+]

First observedSep 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Even though annotations already mark the tool as non-read-only and non-destructive, the description adds substantial behavioral detail: partial update semantics ('omitted fields are left untouched'), clear-flag usage, notes replacement (no append), batch edit behavior, irreversibility, and the need for user confirmation. This goes well beyond the annotations and is valuable for safe invocation.

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

Conciseness4/5

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

The description is dense but well-structured, leading with the core purpose and then layering edge cases and routing guidance. Every sentence contributes, though it is long enough that an agent must read carefully. It is not bloated, just thorough.

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?

For a 15-parameter tool with batch semantics, the description covers the critical gotchas: partial updates, clear list, notes replacement, assignee behavior, label operations, batch irreversibility, and sibling tool routing. An output schema exists, so return-value documentation is not needed. The description is complete for correct invocation.

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 coverage is 100%, so the baseline is 3. The description does reinforce key parameter behaviors (e.g., 'clear' vs empty string, notes replacing existing), but most of the parameter meaning already lives in the schema. It adds marginal but not transformative value over the schema.

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 states a specific verb ('Update') and resource ('one task or several at once'), and explicitly distinguishes itself from sibling tools by saying it does not change status or checklist items. This is a textbook example of sibling differentiation.

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?

The description gives explicit when-to-use ('Update fields on one task or several'), when-not-to-use ('For status changes use task_done, task_reopen or task_archive, and for checklist items use checklist'), and even operational guidance ('confirm the list with the user first' for batch edits). This covers both alternatives and user-facing workflow.

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

All Done Bear 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?