Skip to main content
Glama
estrenuo

OmniFocus MCP Server

by estrenuo

Update Task Note

omnifocus_update_task_note
Idempotent

Update a task's note by ID or name. Supports replacing, clearing, or appending to the existing note content in OmniFocus.

Instructions

Update the note/description on an existing task in OmniFocus.

Use either the task ID or task name to identify the task.

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.

  • note (string): The new note content. Use empty string to clear the note.

  • append (boolean): If true, append to existing note instead of replacing (default: false)

Returns: The updated task object

Examples:

  • Set note by ID: { taskId: "abc123", note: "Remember to include charts" }

  • Set note by name: { taskName: "Write report", note: "Draft due Friday" }

  • Clear note: { taskId: "abc123", note: "" }

  • Append to note: { taskId: "abc123", note: "\nAdditional info here", append: true }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYesThe new note content for the task. Use empty string to clear the note.
appendNoIf true, append to existing note instead of replacing it
taskIdNoThe task ID to update. Takes priority if both taskId and taskName are provided.
taskNameNoThe task name to search for. Used if taskId is not provided.
Behavior5/5

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

Beyond annotations (idempotentHint=true, destructiveHint=false), description clarifies the append behavior, clearing note with empty string, and return value. 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?

Description is concise with clear sections (Args, Returns, Examples). Every sentence adds value; no fluff.

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 specifies the return value. Covers all parameters, edge cases (clear, append), and examples. Highly complete for a simple tool.

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%. The description adds meaning: priority between taskId/taskName, examples for each usage, and append semantics. Exceeds 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 the verb 'update' and resource 'note/description' on a task, and is distinct from sibling tools like omnifocus_update_task (which updates other fields) and omnifocus_update_project_note.

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 taskId vs taskName with priority rules, and shows examples. It doesn't explicitly exclude alternatives but the purpose is clear for note updates.

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