Skip to main content
Glama

task_reorder

Reorder an OmniFocus task among its siblings by placing it before or after another task, or at the start or end of a container.

Instructions

Reorder an OmniFocus task among its siblings. OmniFocus has no numeric sibling index — position is always expressed relative to another task (before / after) or as the absolute start / end of a container. Do NOT use task_reorder to reparent a task to a different project or parent (task_move handles reparenting); prefer task_move when the task needs to change containers without caring about sibling order. Exactly one positioning form must be set: { before }, { after }, or { at, in }. Returns { reordered: true, id, position }. Side effects: changes sibling order in OmniFocus, sets meta.syncPending = true. Example: task_reorder({ id: "abc123", before: "abc456" }) Example: task_reorder({ id: "abc123", at: "start", in: { projectId: "prj456" } })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
atNoAbsolute position within a container. Requires `in` to identify the container.
idYesPersistent ID of the task to reorder.
inNoRequired when `at` is set; ignored otherwise.
afterNoPosition the task immediately after this sibling. Reference must share the same parent.
beforeNoPosition the task immediately before this sibling. Reference must share the same parent.
Behavior5/5

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

No annotations provided, so description fully covers behavior. Discloses side effects (changes sibling order, sets meta.syncPending = true), return structure, and the fact that OmniFocus has no numeric sibling index. 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.

Conciseness5/5

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

Well-structured with clear, front-loaded purpose. Each sentence adds value: purpose, constraint, sibling differentiation, return format, side effects, examples. No redundant or vague statements.

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?

Despite no output schema and complex parameters, the description covers all essential aspects: return values, side effects, constraints, and examples. It is fully self-contained and leaves no major gaps for agent invocation.

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 100% (baseline 3). Description adds significant value by explaining the three positioning forms (before, after, at+in) and that exactly one must be set, plus two examples. This goes beyond the schema's individual parameter descriptions.

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?

Description clearly states 'Reorder an OmniFocus task among its siblings' with a specific verb and resource. It explicitly distinguishes from 'task_move' by noting that reparenting is handled by that sibling tool, making the differentiation strong.

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 ('reorder among siblings') and when not to use ('Do NOT use to reparent'), along with the alternative ('prefer task_move'). Also states the constraint that exactly one positioning form must be set.

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/torsday/omnifocus-mcp'

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