Skip to main content
Glama

move_task

Move a task to a new parent while preserving its uniqueID, dependencies, and resource assignments.

Instructions

Reparent a task without changing its uniqueID.

Wraps the omniJS task.move(newParent, index) method introduced in OmniPlan 4.10.3 (build v232.5.9, 2026-05-06). Both omniJS args are required at the API level; this tool fills in index with newParent.subtasks.length (append at end) when the caller omits it.

Because uniqueID is preserved across the move, dependencies and resource assignments that reference the moved task stay intact — no clone-and-rebuild required.

Args: task_id: uniqueID of the task to move. new_parent_id: uniqueID of the destination parent. If omitted, the task is moved to the document root. index: 0-based position in new_parent.subtasks after the move. If omitted, the task is appended at the end.

Returns: JSON {moved: true, id, new_parent_id, index} where id is the unchanged uniqueID, new_parent_id is the resolved parent's uniqueID (root's -1 if moved to root), and index is the final position used.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes
new_parent_idNo
indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: preserves uniqueID, maintains dependencies/resource assignments, fills in index when omitted, and specifies the underlying omniJS method and version. No contradictions.

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?

The description is well-structured with clear sections (main purpose, context, Args, Returns). While slightly lengthy, every sentence serves a purpose. Front-loaded with the core 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?

Given the complexity of reparenting and the existence of sibling tools like move_resource, the description covers inputs, behavior, output format, edge cases (omitted params), and version requirements. It is fully self-contained.

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 description coverage is 0%, but the description's Args section explains all three parameters: task_id (required), new_parent_id (defaults to root), index (defaults to append at end). This adds complete meaning beyond the schema's type and required fields.

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 'Reparent a task without changing its uniqueID.' It uses specific verbs ('reparent') and distinguishes from alternative approaches (clone-and-rebuild) by emphasizing preservation of uniqueID, dependencies, and assignments.

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

Usage Guidelines4/5

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

The description implicitly guides usage by highlighting when to use (to preserve uniqueID and dependencies) but does not explicitly mention when not to use or enumerate alternatives like delete_task+create_task. The context is clear but lacks explicit exclusions.

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