Skip to main content
Glama
estrenuo

OmniFocus MCP Server

by estrenuo

Update Task

omnifocus_update_task

Update any property of an existing OmniFocus task, including name, due date, notes, flag, estimate, recurrence, or project assignment.

Instructions

Update properties of an existing task in OmniFocus.

Only the fields you provide are changed. Use null to clear a date or note field.

Args:

  • taskId (string, optional): The task's ID. Takes priority if both taskId and taskName provided.

  • taskName (string, optional): The task's name to search for. At least one of taskId or taskName is required.

  • name (string, optional): New task name

  • note (string | null, optional): New note text. Pass null to clear.

  • dueDate (string | null, optional): New due date in ISO 8601 format. Pass null to clear.

  • deferDate (string | null, optional): New defer date in ISO 8601 format. Pass null to clear.

  • plannedDate (string | null, optional): New planned date in ISO 8601 format. Pass null to clear.

  • flagged (boolean, optional): Set flagged state

  • estimatedMinutes (number, optional): Time estimate in minutes. Pass 0 to clear.

  • projectId (string, optional): ID of the project to move the task to.

  • projectName (string, optional): Name of the project to move the task to. Ignored if projectId is provided.

  • recurrence (object | null, optional): Repetition pattern to make the task recurring (same shape as create_task: frequency, interval, daysOfWeek, dayOfMonth, monthOfYear, repeatFrom). Pass null to remove recurrence.

  • clearRecurrence (boolean, optional): Set true to remove the task's repetition rule (turn off recurring). Equivalent to recurrence: null.

Returns: The updated task object

Examples:

  • Rename: { taskId: "abc123", name: "New name" }

  • Set due date: { taskId: "abc123", dueDate: "2024-12-31T17:00:00" }

  • Clear due date: { taskId: "abc123", dueDate: null }

  • Make it recurring weekly: { taskId: "abc123", recurrence: { frequency: "weekly", daysOfWeek: ["Monday"] } }

  • Turn off recurring: { taskId: "abc123", clearRecurrence: true }

  • Flag and estimate: { taskId: "abc123", flagged: true, estimatedMinutes: 30 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew task name
noteNoNew note text. Pass null to clear the note.
taskIdNoThe task ID to update. Takes priority if both taskId and taskName are provided.
dueDateNoNew due date in ISO 8601 format. Pass null to clear.
flaggedNoSet flagged state
taskNameNoThe task name to search for. At least one of taskId or taskName is required.
deferDateNoNew defer/start date in ISO 8601 format. Pass null to clear.
projectIdNoID of the project to move the task to.
recurrenceNoSet a repetition pattern to make the task recurring (same shape as create_task). Pass null to remove recurrence.
plannedDateNoNew planned date in ISO 8601 format. Pass null to clear.
projectNameNoName of the project to move the task to. Ignored if projectId is provided.
clearRecurrenceNoSet true to remove the task's repetition rule (turn off recurring). Equivalent to recurrence: null.
estimatedMinutesNoEstimated time in minutes. Pass 0 to clear.
Behavior5/5

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

The description adds context beyond annotations by detailing partial update behavior, null clearing, taskId/taskName priority, and return value. Annotations are consistent (write operation, not destructive, not idempotent).

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 long but well-structured with Args, Returns, and Examples sections. It is front-loaded with purpose. Minor redundancy (e.g., clearRecurrence explanation could be shorter) but overall efficient.

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 13 parameters and no output schema, the description covers all parameters, return value, special behaviors (null clearing, priority), and multiple examples. It is complete for a complex update tool.

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%, and the description adds significant meaning: structured breakdown of all 13 parameters, type info, null handling, and examples. It references 'same shape as create_task' for recurrence, adding clarity.

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 'Update properties of an existing task in OmniFocus' with a specific verb and resource. It distinguishes from siblings like create_task, complete_task, and delete_task by focusing on updating existing tasks.

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 explains partial updates ('Only the fields you provide are changed'), how to clear fields with null, and priority between taskId and taskName. It provides examples but does not explicitly contrast with alternative tools like omnifocus_update_task_note or batch tools.

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

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