Skip to main content
Glama

batch_create_tasks

Create multiple tasks at once by providing a list of task objects. Each task requires a title; returns a mapping of IDs to etags and reports any errors.

Instructions

Create multiple tasks at once via V2 batch.

[Category: Tasks — Batch]  [Auth: V2]
[Related: create_task, batch_update_tasks, batch_delete_tasks]

⚠️ SUBTASK TRAP — parentId in the task dict is SILENTLY IGNORED here too (V2 batch).
Do NOT pass parentId expecting subtask relationships to be created automatically.
ALWAYS call set_subtask_parent for each child AFTER this call.

Args:
    tasks: List of task dicts. Each needs at least {"title": "..."}.
        Optional: projectId, content, priority, dueDate, startDate,
        timeZone, tags, allDay, kind, items, columnId.
        ⚠️ Do NOT include parentId — use set_subtask_parent instead.

Returns: {id2etag: {id: etag}, id2error: {id: error}} — check id2error for failures.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tasksYes
Behavior5/5

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

Discloses a critical behavioral trap: parentId is silently ignored. Also describes return format and the need to check id2error. Since no annotations are provided, this description fully covers behavioral traits.

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?

Well-structured with sections, warnings, and a clear Args/Returns breakdown. Every sentence is purposeful, no wasted words. Front-loaded with the main action.

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?

For a single-parameter tool with no output schema, the description covers input requirements, output format, error handling, and the critical subtask trap. No gaps remain.

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?

The input schema has 0% coverage (only 'tasks' as array of objects with additionalProperties: true). The description adds essential meaning: required 'title', optional fields, and explicitly warns against including parentId. This fully compensates for the minimal 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?

The description clearly states 'Create multiple tasks at once via V2 batch', with a specific verb and resource. It distinguishes from sibling tools like create_task, batch_update_tasks, and batch_delete_tasks.

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?

Explicit guidance on when to use this tool vs alternatives, including a warning not to pass parentId and to use set_subtask_parent instead. Lists related tools for context.

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