Skip to main content
Glama

task_batch_uncomplete

Batch revert multiple completed OmniFocus tasks to active status in a single operation. Reverses accidental completions or tasks needing redo.

Instructions

Mark many OmniFocus tasks as incomplete in a single JXA round trip. Reverses a previous completion — useful when a task was completed by mistake or needs to be re-done. Uncompleted tasks return to active status. Use task_batch_complete to mark tasks as completed. Validation is atomic: if any input fails schema, the whole batch is rejected before any mutation. Execution is best-effort: each uncomplete succeeds or fails independently, and the response reports per-index outcomes. Prefer this tool over repeated task_uncomplete calls whenever uncompleting more than one task. Each item is { id }. Returns { uncompleted: [{index, value: { id, name }}], failed: [{index, errorCode, message}] } — value carries the task name so the agent can describe each restoration without a follow-up read. Side effects: writes to OmniFocus, sets meta.syncPending = true. Call sync_trigger when you need changes to appear on other devices. Example: task_batch_uncomplete({ items: [{ id: "abc123" }, { id: "abc456" }] })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesArray of { id } items. Must contain at least one item.
idempotency_keyNoIdempotency key for retry-safe batches. Replays within the TTL window return the cached envelope with meta.idempotentReplay = true. See docs/idempotency.md.
Behavior4/5

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

No annotations provided, so description carries full burden. It explains atomic validation, best-effort execution with per-index outcomes, side effects (writes to OmniFocus, sets syncPending), and return format. Lacks mention of authentication or rate limits, but sufficient for most use cases.

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?

Concise and front-loaded with purpose. Every sentence adds value: purpose, use case, behavior, return format, side effects, example. No redundancy.

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, description fully documents return values with structure and purpose (task name for agent usage). Covers validation, execution model, side effects, and sync dependency. Complete for agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline 3. Description adds minimal extra meaning beyond schema (example, mentions { id } each item), but does not elaborate on idempotency_key usage or pattern beyond schema. Adequate.

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?

Clearly defines verb ('Mark many OmniFocus tasks as incomplete'), resource ('OmniFocus tasks'), and scope ('batch'). Distinguishes from sibling tools like task_batch_complete and task_uncomplete by emphasizing batch nature and reversal of completion.

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?

Provides explicit preference over repeated task_uncomplete for batches, and explains atomic validation and best-effort execution. Could be more explicit about when to use task_uncomplete for single tasks, but context is clear from siblings.

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