Done Bear MCP

List Tasks

task_list

Read-only

List tasks in the workspace, most recently updated first. Completed tasks are ordered by completion time, newest first. Filter by view (inbox, today, upcoming, anytime, someday, logbook, trash) and/or state (open, done, archived, all); search ranks matches within that filter. view: "logbook" reads completed tasks and view: "trash" archived ones, whatever state says. Returns up to limit tasks; hasMore is true when more matched than were returned, and passing nextCursor back as cursor reads the next page. To find a task by its words across every view use search instead, and task_show for one task's checklist, comments and files.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`view`	No	Filter by GTD view bucket. logbook and trash read the completed and archived tasks regardless of `state`
`limit`	No	Max results
`state`	No	Filter by task state	open
`cursor`	No	Opaque pagination cursor from a previous call's `nextCursor`. Pass it with the same filters to fetch the next page.
`search`	No	Ranked lexical search over title/description; when set, results are ordered by relevance instead of recency
`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."
`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. Required when the account has more than one workspace: a call without it then fails and names the choices

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes
`tasks`	Yes
`total`	Yes
`hasMore`	Yes	True when more results matched than were returned
`nextCursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed22 schema fields changedOct 5, 2026
- addedOutput schema / properties / nextCursor / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / nextCursor / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / tasks / items / properties / agentAssigneeId / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / tasks / items / properties / agentAssigneeId / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / tasks / items / properties / assigneeId / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / tasks / items / properties / assigneeId / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / tasks / items / properties / completed / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / tasks / items / properties / completed / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / tasks / items / properties / completedAt / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / tasks / items / properties / completedAt / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / tasks / items / properties / deadline / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / tasks / items / properties / deadline / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / tasks / items / properties / description / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / tasks / items / properties / description / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / tasks / items / properties / projectId / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / tasks / items / properties / projectId / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / tasks / items / properties / startDate / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / tasks / items / properties / startDate / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / tasks / items / properties / teamId / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / tasks / items / properties / teamId / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / tasks / items / properties / view / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / tasks / items / properties / view / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

Changed3 schema fields changedOct 2, 2026

addedOutput schema / properties / tasks / items / properties / agentAssigneeId
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

addedOutput schema / properties / tasks / items / properties / revision

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

changedOutput schema / properties / tasks / items / required

Previous value: -[
-  "assigneeId",
-  "completed",
-  "completedAt",
-  "deadline",
-  "description",
-  "id",
-  "number",
-  "projectId",
-  "startDate",
-  "state",
-  "teamId",
-  "title",
-  "view"
-]New value: +[
+  "agentAssigneeId",
+  "assigneeId",
+  "completed",
+  "completedAt",
+  "deadline",
+  "description",
+  "id",
+  "number",
+  "projectId",
+  "revision",
+  "startDate",
+  "state",
+  "teamId",
+  "title",
+  "view"
+]

Changed20 schema fields changedSep 30, 2026
- removedOutput schema / properties / nextCursor / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / nextCursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / tasks / items / properties / assigneeId / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tasks / items / properties / assigneeId / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / tasks / items / properties / completed / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tasks / items / properties / completed / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / tasks / items / properties / completedAt / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tasks / items / properties / completedAt / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / tasks / items / properties / deadline / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tasks / items / properties / deadline / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / tasks / items / properties / description / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tasks / items / properties / description / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / tasks / items / properties / projectId / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tasks / items / properties / projectId / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / tasks / items / properties / startDate / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tasks / items / properties / startDate / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / tasks / items / properties / teamId / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tasks / items / properties / teamId / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / tasks / items / properties / view / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tasks / items / properties / view / type
```
Added value: +[
+  "string",
+  "null"
+]
```

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"

Changed2 schema fields changedSep 5, 2026

addedOutput schema / properties / tasks / items / properties / completedAt

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Completion instant in UTC (ISO 8601), or null for an unfinished task"
+}

changedOutput schema / properties / tasks / items / required

Previous value: -[
-  "assigneeId",
-  "completed",
-  "deadline",
-  "description",
-  "id",
-  "number",
-  "projectId",
-  "startDate",
-  "state",
-  "teamId",
-  "title",
-  "view"
-]New value: +[
+  "assigneeId",
+  "completed",
+  "completedAt",
+  "deadline",
+  "description",
+  "id",
+  "number",
+  "projectId",
+  "startDate",
+  "state",
+  "teamId",
+  "title",
+  "view"
+]

Changed4 schema fields changedSep 4, 2026

changedInput schema / properties / view / description

Previous value: -"Filter by GTD view bucket"New value: +"Filter by GTD view bucket. logbook and trash read the completed and archived tasks regardless of `state`"

changedInput schema / properties / view / enum

Previous value: -[
-  "inbox",
-  "anytime",
-  "today",
-  "upcoming",
-  "someday"
-]New value: +[
+  "inbox",
+  "anytime",
+  "today",
+  "upcoming",
+  "someday",
+  "logbook",
+  "trash"
+]

addedOutput schema / properties / tasks / items / properties / completed

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The date (YYYY-MM-DD) the task was completed, in the requested timezone. Null while it is still open"
+}

changedOutput schema / properties / tasks / items / required

Previous value: -[
-  "assigneeId",
-  "deadline",
-  "description",
-  "id",
-  "number",
-  "projectId",
-  "startDate",
-  "state",
-  "teamId",
-  "title",
-  "view"
-]New value: +[
+  "assigneeId",
+  "completed",
+  "deadline",
+  "description",
+  "id",
+  "number",
+  "projectId",
+  "startDate",
+  "state",
+  "teamId",
+  "title",
+  "view"
+]

First observedSep 1, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description goes well beyond them by disclosing ordering rules, pagination contract (limit/hasMore/nextCursor round-trip), and the state-override behavior of logbook and trash views. That is real operational context an agent cannot infer from annotations.

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?

Front-loaded with the core action and ordering, then the filter semantics, then pagination, then sibling routing — a logical progression with no filler sentences. It is somewhat dense and partially restates the view enum already present in the schema, which is the only slack.

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 an 8-parameter list tool with a 100% documented schema and an output schema, the description covers everything an agent needs: scope, default ordering, filter precedence, search behavior, pagination, and alternatives. Nothing required to call it correctly is missing.

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 genuine semantics: the enumerated view buckets, that logbook/trash read completed/archived regardless of state, that search reorders results by relevance rather than recency, and how cursor pairs with the same filters. Only minor duplication of schema content keeps it from a 5.

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 and resource ('List tasks in the workspace') plus the default ordering ('most recently updated first'). It also explicitly distinguishes itself from two named siblings, search and task_show, so an agent can route correctly without opening any schema.

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 routing rules: use search to find a task by its words across every view, and task_show for a single task's checklist, comments and files. It also explains the view/state interaction and the precedence rule that logbook/trash override state.

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?