Done Bear

Search Tasks

search

Read-only

Search tasks across the workspace. Ranked lexical search over title and description: exact and prefix matches rank first, then word-boundary, substring, and fuzzy matches, with recency and status factored in. Multi-word queries match in any order. Searches every state by default, completed and archived included. Use this when the user names a task by its words; use task_list to browse a view (Today, Inbox, …) and task_show once you have the task number.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max results
`query`	Yes	Search query (matches title and description)
`state`	No	Filter by task state	all
`cursor`	No	Opaque pagination cursor from a previous call's `nextCursor`. Pass it with the same filters to fetch the next page.
`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
`query`	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"
+]

Changed2 schema fields changedSep 4, 2026

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 declare this a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds non-obvious behavior on top: every state is searched by default including completed and archived, results are ranked by match class with recency and status as tiebreakers, and multi-word queries match in any order. These are exactly the surprises an agent would otherwise get wrong when interpreting results.

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?

Five sentences, each carrying a distinct payload: identity, ranking behavior, multi-word handling, default state scope, and sibling routing. The ranking sentence is the longest but is the tool's core differentiator, and the routing instruction is correctly placed last as a disambiguation. No filler or repetition of the tool title.

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 return values and the nextCursor pagination contract need not be restated. With 100% schema coverage on all seven parameters, annotations covering the safety profile, and the description covering ranking semantics, default scope, and sibling routing, an agent has everything needed to call this correctly.

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 description coverage is 100%, so the baseline is 3 and the schema already documents limit, cursor, state, timezone, workspace, and context. The description goes beyond that baseline by explaining what the query string actually matches against and how multi-word queries are combined, which is real semantic value for the primary parameter.

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 ('Search tasks across the workspace') and immediately narrows it to a ranked lexical search over title and description, which is a distinct mechanism from browsing. It explicitly names the siblings task_list and task_show and the condition that distinguishes them, so an agent can route 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 an explicit trigger ('when the user names a task by its words') and names two alternatives with their own triggers: task_list to browse a view such as Today or Inbox, and task_show once the task number is known. When-to-use and when-not-to-use are both present, with no inference required.

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?