Skip to main content
Glama

batch_create_tasks

Create multiple independent tasks in a single call with per-task success reporting. Use for batch task creation without parent dependencies.

Instructions

Create multiple tasks in a single call with per-task result reporting.

Prefer this over repeated create_task calls when creating several independent tasks at once. Use create_subtask instead when tasks must be linked to a parent via depends. Requires GENERATOR role.

NON-ATOMIC: tasks are created sequentially. If task N fails, tasks 0..N-1 are already committed — there is no rollback. A rate-limit hit stops the batch early; partial results are returned with the stopping index and created/failed counts.

dry_run=true previews all entries without writing to Taskwarrior. Each preview entry confirms field validation without mutation.

Each entry in tasks accepts: description (str, required), project (str), priority (H/M/L), tags (list[str] or comma-separated str), due (ISO or TW relative e.g. eow/eom), extra_fields (dict of UDA key/value pairs).

Call get_schema_info first to confirm required and available fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tasksYes
dry_runNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses non-atomicity (no rollback), sequential creation, rate-limit behavior, partial results, dry_run preview behavior. No annotations provided, so description bears full burden and does so thoroughly.

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 clear sections, but slightly lengthy. Every sentence adds value; could be slightly more concise but effective.

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 all critical aspects: purpose, usage guidance, behavioral details, parameter specifics, prerequisite (get_schema_info), and role requirement. No gaps given the tool's complexity.

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 coverage is 0%, but description compensates fully by detailing each field in the 'tasks' array: description, project, priority, tags, due, extra_fields. Also explains dry_run.

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 the tool creates multiple tasks in a single call with per-task result reporting. It distinguishes from siblings like create_task and create_subtask.

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 states when to prefer this over create_task and when to use create_subtask instead. Also mentions required GENERATOR role and recommends calling get_schema_info first.

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/GabiUp2/TaskChampion_MCP'

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