Skip to main content
Glama

create_tasks

Batch-create multiple OmniPlan tasks in a single call to reduce overhead. Specify each task's title, dates, effort, and optional parent references.

Instructions

Create multiple tasks in a single JXA call.

Performance: each evaluateJavascript round-trip is ~1-3s of osascript startup. Building 50 tasks via 50 calls to create_task is ~50-150s. This tool does the whole batch in one round-trip.

Args: tasks: list of task specs. Each spec is a dict with the same fields create_task accepts: title (required), parent_id, task_type, note, manual_start_date, manual_end_date, effort_seconds, min_effort_seconds, expected_effort_seconds, max_effort_seconds. Plus one extra: parent_index — int, optional. References another task in the same batch by zero-based position. Must be less than the task's own index. At most one of parent_id and parent_index may be set; if neither is set, the task is added under the document root.

Returns: JSON array of created-task shapes — same fields as create_task returns, in the order the inputs were given.

Raises ValueError on invalid parent_index references or unknown parent_id, before any task is created.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tasksYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are present, so the description carries full burden. It discloses performance characteristics (1-3s per round-trip), atomic validation (raises ValueError before any creation), and batching behavior. However, it does not explicitly state whether the operation is fully transactional or mention required permissions.

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?

The description is well-structured with clear sections (Performance, Args, Returns, Raises). Every sentence adds value—no fluff. It is appropriately sized for the tool's complexity.

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?

Given the output schema exists, the description still adds useful return details. It covers error handling, parameter constraints, and performance context. All relevant aspects are addressed for an agent to invoke the tool correctly.

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 the description provides exhaustive semantics for the `tasks` parameter: lists accepted fields (title, parent_id, etc.), explains the extra `parent_index` field, and clarifies constraints (at most one of parent_id/parent_index). This fully compensates for the schema's lack of detail.

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 opens with a specific verb and resource: 'Create multiple tasks in a single JXA call.' It clearly distinguishes from the sibling `create_task` by highlighting the batch nature.

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?

Provides explicit guidance on when to use this tool over `create_task` by quantifying the performance cost of multiple individual calls (50-150s) versus one batch call.

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/johntrandall/omniplan-mcp'

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