Create, update, or delete multiple TickTick tasks in a single request to simplify bulk task management.
Creates, updates and/or deletes many tasks in one request. Note: some accounts are gated and receive 403 for batch writes.
| Name | Required | Description | Default |
|---|---|---|---|
| add | No | Tasks to create | |
| delete | No | Tasks to delete, as { taskId, projectId } | |
| update | No | Tasks to update |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so the description carries the behavioral burden. It discloses bulk mutation and a 403 gating condition for some accounts, but omits atomicity/partial-failure behavior, maximum batch size, and exact permission requirements.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the operations and followed by a useful caveat. Every sentence earns its place with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema and no annotations. For a batch mutation tool, the description should ideally explain response shape, partial success handling, and limits; it covers operations and gating but leaves these important gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with add, update, and delete documented, so baseline 3. The description adds no syntax or item-shape detail beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Names three operations (creates, updates, deletes), the resource (tasks), and the batch scope (many tasks in one request), clearly distinguishing it from the single-task CRUD siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies use when handling multiple tasks at once, but does not explicitly say to prefer it over create_task/update_task/delete_task for single records. The 403 gating note adds a usage constraint but no alternatives guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.