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

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

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.

Changed12 schema fields changedNov 3, 2026
- 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 / duration / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tasks / items / properties / duration / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / tasks / items / properties / note / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tasks / items / properties / note / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / tasks / items / properties / reminder / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tasks / items / properties / reminder / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / tasks / items / properties / source / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tasks / items / properties / source / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / tasks / items / properties / when / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tasks / items / properties / when / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed2 schema fields changedOct 29, 2026

addedOutput schema / properties / tasks / items / properties / reminder

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Time of day on the `when` day, \"HH:MM\", or null for none."
+}

changedOutput schema / properties / tasks / items / required

Previous value: -[
-  "id",
-  "url",
-  "name",
-  "completed",
-  "starred",
-  "when",
-  "note",
-  "duration",
-  "completedAt",
-  "updatedAt",
-  "source",
-  "list"
-]New value: +[
+  "id",
+  "url",
+  "name",
+  "completed",
+  "starred",
+  "when",
+  "reminder",
+  "note",
+  "duration",
+  "completedAt",
+  "updatedAt",
+  "source",
+  "list"
+]

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.1/5.0

Behavior4/5

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

Annotations already declare a safe read-only, closed-world operation, and the description adds real behavior: the default unfiltered scope and the optionality of text search, which an agent would otherwise have to infer. Pagination exists in the schema but the description's single cursor sentence is only covered via the parameter, not explained here.

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 short sentences, front-loaded with purpose and default behavior, followed by the optionality note and the sibling cross-reference. No redundant wording and nothing buried.

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

Completeness4/5

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

Output schema covers return values and the full schema covers filter syntax, so the description only needs to set scope and prerequisites, which it does. A brief note on result ordering or default sort would close the remaining gap.

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 value for listId by telling the agent to resolve a list to its id via view_lists first. It also clarifies that query is optional and that a bare call needs no parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Search the user's tasks") and clarifies scope with "A bare call returns tasks from every list." It does not explicitly contrast itself with view_task, but the mention of view_lists for id resolution shows awareness of the sibling set.

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?

Gives clear when-to-use context: omit filters to span every list, text search is optional, and call view_lists first to resolve a list name to an id. It stops short of naming when another sibling (e.g. view_task) should be used instead.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?