Skip to main content
Glama

batch_update_tasks

Update multiple tasks in a single request. Provide a list of task dicts including their IDs and fields to change.

Instructions

Update multiple tasks at once via V2 batch.

[Category: Tasks — Batch]  [Auth: V2]
[Related: update_task, batch_create_tasks, batch_delete_tasks]

Args:
    tasks: List of task dicts. Each MUST include "id" and "projectId"
        plus fields to change. ⚠️ No read-modify-write — provide full field values.

⚠️ REMINDER RELIABILITY — DO NOT USE THIS TOOL FOR REMINDER UPDATES:
batch_update_tasks() uses the V2 batch endpoint which cannot reliably set reminders
on existing tasks, for two compounding reasons:
  1. V2-created tasks may have dueDate invisible to V1 (null), breaking reminder anchoring.
  2. Reminder object format {"trigger": "TRIGGER:-P2DT0H0M0S"} is silently rejected by the
     V2 batch endpoint — no error returned, but reminders are never saved.
PREFERRED PATTERN: use update_task() (V1) with explicit due_date + time_zone + reminder_minutes.
See the "Add/update reminders" workflow in ticktick_guide(show_workflows=True).

Returns: {id2etag, id2error}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tasksYes
Behavior5/5

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

Discloses limitations of V2 batch for reminders, explains silent rejection and dueDate invisibility, and states response format. No annotations provided, so description carries full burden.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with sections and warnings, but slightly lengthy. All content is relevant; no redundancy.

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

Completeness5/5

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

Covers purpose, parameters, caveats, alternatives, and response format comprehensively for a batch update tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage and param is untyped. Description adds critical detail: each task dict must include 'id' and 'projectId', full field values required, no read-modify-write.

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?

Clearly states 'Update multiple tasks at once via V2 batch' and includes 'Category: Tasks — Batch' and 'Related: update_task, batch_create_tasks, batch_delete_tasks'. Distinguishes from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly warns not to use for reminder updates, explains why, and directs to preferred pattern using update_task(). Also mentions read-modify-write caveat.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/KpihX/tick-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server