Taskaid

Create or update a list

save_list

Destructive

Upsert a list. Omit id to create a new one (name required). Pass id to rename an existing list, change its emoji or rewrite its note. Returns the saved list.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	List id. Pass to update an existing list; omit to create a new one.
`name`	No	Required when creating. On update, omit to keep the current name.
`note`	No	A note about the list, as Markdown, up to 500 characters: what it is for and how its tasks are handled. Replaces the whole note; null clears it.
`emoji`	No	A single emoji shown before the list name. Defaults to 📋 when creating; omit on update to keep the current one.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`note`	Yes
`emoji`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 14, 2026

addedInput schema / properties / note

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "A note about the list, as Markdown, up to 500 characters: what it is for and how its tasks are handled. Replaces the whole note; null clears it."
+}

addedOutput schema / properties / note

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "id",
-  "emoji",
-  "name"
-]New value: +[
+  "id",
+  "emoji",
+  "name",
+  "note"
+]

Changed2 schema fields changedSep 7, 2026

addedInput schema / properties / emoji / description

Added value: +"A single emoji shown before the list name. Defaults to 📋 when creating; omit on update to keep the current one."

addedInput schema / properties / name / description

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

First observedSep 7, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations declare destructiveHint=true, so the agent knows updates can overwrite. The description notes that note is replaced entirely and emoji/name can be kept, which adds context beyond annotations. It doesn't mention permissions, reversibility, or rate limits, but covers the mutation semantics reasonably.

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: verb+resource first, then create/update conditions, then return value. Every sentence earns its place and is front-loaded.

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, the description doesn't need to explain returns. It covers create/update logic well, but for a destructive mutation it could mention what happens to unspecified fields (though the schema covers it). Overall, adequate for the tool's complexity.

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 coverage is 100%, so parameter meanings are fully documented in the schema. The description reinforces the id semantics and the note replacement behavior, adding some value, but doesn't exceed what the schema already provides.

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?

The description states a specific verb (upsert) and resource (list), and distinguishes create from update by the presence of id. An agent can tell it apart from the sibling save_plan, save_task, and view_list tools.

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?

It clearly explains the create vs. update conditions ('Omit id to create... Pass id to rename...'), but it doesn't explicitly say when to use this tool versus the sibling save_task or save_plan, which might be confusing for an agent. Still, the create/update guidance 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

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?