Taskaid

Search tasks

search_tasks

Read-only

Search the user's tasks. A bare call returns tasks from every list. Text search is optional. Use view_lists to resolve a list to its id.

Input Schema

TableJSON Schema

Name	Required	Description
`when`	No	Narrow by scheduled day. Each bound is a day, "2026-09-19", or an ISO 8601 duration from today in the user's timezone: "P0D" is today, "P1D" tomorrow, "-P1D" yesterday, "P2W" two weeks out. Inbox tasks have no day and never match.
`limit`	No	Max results. Defaults to 50, up to 100.
`query`	No	Narrow to tasks matching this text. Every whitespace-separated word must appear in the task's name or note (case-insensitive, any order), so extra words narrow the results rather than widening them — pass distinctive keywords, not a full sentence.
`cursor`	No	Continue from a previous response's nextCursor, with the same filters. Omit for the first page.
`listId`	No	Narrow to a single list. Omit to span every list.
`completed`	No	Narrow to finished (true) or open (false) tasks. Omit for both.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tasks`	Yes
`nextCursor`	No	Pass as cursor, with the same filters, to read the next page. Absent on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 24, 2026

changedInput schema / properties / completed / description

Previous value: -"Read finished tasks instead of active ones. Omit for active tasks."New value: +"Narrow to finished (true) or open (false) tasks. Omit for both."

changedInput schema / properties / when / properties / gte / description

Previous value: -"Inclusive lower bound. Omit it for overdue work."New value: +"Inclusive lower bound. Omit it to include every earlier day."

changedInput schema / properties / when / properties / lte / description

Previous value: -"Inclusive upper bound. \"P0D\" alone reads today and everything overdue."New value: +"Inclusive upper bound. With `completed: false`, \"P0D\" alone reads today and everything overdue."

Changed5 schema fields changedSep 15, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "Continue from a previous response's nextCursor, with the same filters. Omit for the first page.",
+  "type": "string"
+}

addedInput schema / properties / when

Added value: +{
+  "description": "Narrow by scheduled day. Each bound is a day, \"2026-09-19\", or an ISO 8601 duration from today in the user's timezone: \"P0D\" is today, \"P1D\" tomorrow, \"-P1D\" yesterday, \"P2W\" two weeks out. Inbox tasks have no day and never match.",
+  "properties": {
+    "gte": {
+      "description": "Inclusive lower bound. Omit it for overdue work.",
+      "type": "string"
+    },
+    "lte": {
+      "description": "Inclusive upper bound. \"P0D\" alone reads today and everything overdue.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

removedOutput schema / properties / hasMore

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

addedOutput schema / properties / nextCursor

Added value: +{
+  "description": "Pass as cursor, with the same filters, to read the next page. Absent on the last page.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "tasks",
-  "hasMore"
-]New value: +[
+  "tasks"
+]

Changed3 schema fields changedSep 11, 2026
- addedInput schema / properties / limit / default
```
Added value: +50
```
- changedInput schema / properties / limit / description
```
Previous value: -"Max results."New value: +"Max results. Defaults to 50, up to 100."
```
- changedInput schema / properties / limit / maximum
```
Previous value: -9007199254740991New value: +100
```
AddedSep 11, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish the read-only, non-destructive profile. The description adds behavioral context beyond that: a bare call returns tasks from every list, and text search is optional. This helps the agent predict the tool's default behavior without restating the full schema.

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: a clear verb-resource statement, a crucial scoping default, and a routing hint. No redundancy with the schema's detailed parameter descriptions.

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?

With all six parameters fully documented in the schema, an output schema present, and annotations covering safety, the description covers the remaining contextual needs: default behavior, optional text search, and how to obtain a list id. Nothing essential 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 value by connecting listId to a concrete sibling operation ('Use view_lists to resolve a list to its id'). This is a meaningful cross-tool hint that the schema alone doesn't provide.

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?

Description opens with a specific verb and resource ('Search the user's tasks') and immediately clarifies scope: a bare call returns tasks from every list. It distinguishes itself from siblings like view_task and view_lists by framing search as a collection-level operation and by naming view_lists as the list-resolution tool.

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

Usage Guidelines4/5

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

The description gives a clear routing hint: 'Use view_lists to resolve a list to its id,' which tells the agent when to consult a sibling tool. It does not explicitly state when to prefer search_tasks over view_task, but the context is sufficient for a sensible selection.

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

All Taskaid 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?