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.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that filtering is optional and that results span every list, but says nothing about pagination behavior or result ordering. That is a modest but real addition on top of the annotations.

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, each front-loading the most important fact: what it searches, the default scope, and how to filter by list. No filler or restatement of the title.

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?

With annotations carrying the safety profile and an output schema present, return values need not be explained. The description covers default scope and the one cross-tool dependency (view_lists for listId), leaving only pagination/ordering behavior unstated, which the cursor field already implies.

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 description coverage is 100%, so every parameter is already documented in detail (duration syntax, word-AND matching, limit bounds, cursor usage). The description reinforces only the omission semantics of listId and query, adding little beyond the schema, so the baseline 3 applies.

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 the user's tasks') and immediately defines the default scope ('a bare call returns tasks from every list'). The cross-reference to view_lists clarifies how it relates to a sibling tool rather than duplicating it.

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 context: text search is optional, a filterless call spans all lists, and listId must be resolved via view_lists. It lacks an explicit when-not-to-use statement (e.g. use view_task for a single known task), so it stops short of full routing guidance.

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

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?