Taskaid

Create or update a task

save_task

Destructive

Upsert a task. Omit id to create a new one (name required). Pass id to update an existing task — any subset of fields. To change part of the note, pass patch instead of note. Use null on listId to unlink a task from its list. Returns the saved task.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Task reference: TASKAID-45, #45 or 45. Pass to update an existing task; omit to create a new one.
`name`	No	Required when creating. On update, omit to keep the current name. A few words naming the action; the day goes in `when`, the detail in `note`.
`note`	No	Task notes, as Markdown, up to 15,000 characters — rendered as rich text in the app. Headings, lists, bold, and inline code are supported. Send literal newlines and characters, not escape sequences.
`when`	No	The day the task is scheduled for, as "YYYY-MM-DD" (e.g. "2026-05-21"). Omit or pass null when creating to leave the task in Inbox; pass null when updating to move it back there.
`patch`	No	Edits to the note, applied in order and atomically — if one fails, nothing is written. Only on update, in place of `note`: text you do not send keeps its exact wording.
`listId`	No	Pass null to unlink the task from its list.
`starred`	No
`duration`	No	Estimated duration in minutes, up to a day. Null clears the estimate.
`completed`	No	Marks the task done. True stamps `completedAt` with the time of the call, never the time the work finished.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`url`	Yes
`list`	Yes
`name`	Yes
`note`	Yes
`when`	Yes	Calendar date, "YYYY-MM-DD", or null for Inbox.
`source`	Yes
`starred`	Yes
`duration`	Yes
`completed`	Yes
`updatedAt`	Yes
`completedAt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

changedInput schema / properties / name / description

Previous value: -"Required when creating. On update, omit to keep the current name."New value: +"Required when creating. On update, omit to keep the current name. A few words naming the action; the day goes in `when`, the detail in `note`."

Changed2 schema fields changedSep 7, 2026

addedInput schema / properties / completed / description

Added value: +"Marks the task done. True stamps `completedAt` with the time of the call, never the time the work finished."

addedInput schema / properties / name / description

Added value: +"Required when creating. On update, omit to keep the current name."

First observedSep 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds the upsert semantics, the null-unlink behavior for listId, and that patch is atomic ('if one fails, nothing is written' is in schema, but description states 'Returns the saved task'). It could say more about what destructive means here (e.g. overwrite vs append), but it covers the key mutation traits beyond 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?

Five short sentences, front-loaded with the upsert core and then the notable edge cases (patch, null listId, return value). Every sentence earns its place.

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 an output schema present and 89% schema coverage, the description needn't explain returns or every param. It is complete enough for a 9-param upsert tool, though it could note that `name` is required on create (it does) and clarify destructive scope slightly more.

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 89%, so the schema carries most parameter detail. The description still adds meaning: null-on-listId unlinking, patch-instead-of-note, and id-omit-creates. It doesn't re-explain every field, which is appropriate given the rich schema.

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 ('Upsert a task') and immediately distinguishes create vs update via the `id` parameter, which separates it from sibling `search_tasks`/`view_task` reads and from `save_list`/`save_plan`. The agent can identify exactly what this tool does.

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 create-vs-update routing ('Omit id to create', 'Pass id to update') and a specific sub-case ('To change part of the note, pass patch instead of note'). It does not explicitly name sibling tools as alternatives, but the when-to-use for create vs update is explicit.

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?