Skip to main content
Glama
estrenuo

OmniFocus MCP Server

by estrenuo

Update Project

omnifocus_update_project

Update an existing OmniFocus project's name, status, dates, notes, or review interval. Change status to active, on hold, done, or dropped; clear dates or notes by passing null.

Instructions

Update properties of an existing project in OmniFocus.

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

Args:

  • projectId (string, optional): The project's ID. Takes priority if both projectId and projectName provided.

  • projectName (string, optional): The project's name to search for. At least one of projectId or projectName is required.

  • name (string, optional): New project name

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

  • status (string, optional): "active", "on hold", "done", or "dropped". Setting "done" completes the project and "dropped" drops it (setting "active" reactivates a completed/dropped project).

  • flagged (boolean, optional): Set flagged state

  • 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.

  • sequential (boolean, optional): Tasks must be done in order (true) or parallel (false)

  • reviewIntervalDays (number, optional): Review interval in days (1-3650)

Note: moving a project between folders is not supported by OmniFocus's JXA layer (the move operation returns "Replacement not supported"). Recreate the project in the target folder if you need to move it.

Returns: The updated project object

Examples:

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

  • Put on hold: { projectId: "abc123", status: "on hold" }

  • Complete the project: { projectId: "abc123", status: "done" }

  • Drop the project: { projectId: "abc123", status: "dropped" }

  • Set review interval: { projectId: "abc123", reviewIntervalDays: 14 }

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew project name
noteNoNew note text. Pass null to clear the note.
statusNoNew project status
dueDateNoNew due date in ISO 8601 format. Pass null to clear.
flaggedNoSet flagged state
deferDateNoNew defer/start date in ISO 8601 format. Pass null to clear.
projectIdNoThe project ID to update. Takes priority if both projectId and projectName are provided.
sequentialNoIf true, tasks must be completed in order (sequential). If false, parallel.
projectNameNoThe project name to search for. At least one of projectId or projectName is required.
reviewIntervalDaysNoReview interval in days.
Behavior5/5

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

The description discloses important behaviors: only provided fields are changed, null clears fields, status transitions (completing with 'done' vs 'dropped', reactivation). It also transparently notes the unsupported move operation with an explanation. This goes beyond the basic annotations (which only indicate non-readOnly).

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 somewhat lengthy but well-structured: purpose first, then parameter details, then a note on limitation, then returns, then examples. Every sentence adds value. A minor deduction for verbosity; could be more terse for agent consumption, but still effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 10 parameters, no output schema, and no nested objects, the description covers all parameters with examples and notes limitations. It mentions return value ('The updated project object') but doesn't detail its structure. However, without an output schema, this is adequate. The description is complete enough for an agent to use correctly.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by explaining usage semantics: null clears fields, status effects (e.g., setting 'done' completes), and the priority between projectId/projectName. Examples further clarify parameter usage. This raises the score above baseline.

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 project in OmniFocus,' specifies the specific fields that can be updated, and distinguishes itself from siblings like omnifocus_update_project_note and omnifocus_create_project. It also notes a limitation (moving folders not supported) which clarifies scope.

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 when to use this tool: for updating any project property. It provides constraints like the priority of projectId over projectName and the requirement of at least one identifier. It also warns about the unsupported move operation. However, it does not explicitly guide the agent on when to choose this over other update tools like omnifocus_update_project_note, though the sibling names imply the distinction.

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