Skip to main content
Glama
GlassyWorld

OmniFocus MCP Server

by GlassyWorld

create_task

Idempotent

Create a new OmniFocus task in the inbox, a project, or under a parent task. Optionally attach up to 5 existing tags.

Instructions

Create exactly one new OmniFocus task after an explicit user request. destination is required: Inbox, one exact Active Project canonical ID from a fresh get_project read, or one exact existing ordinary Action Group canonical ID from a fresh get_task read. Parent names, paths, leaf Actions, and Project roots are never accepted as Parent destinations. Optional tagIds accepts 1-5 unique canonical IDs of existing Active Tags selected from fresh search_tags results; names and paths are never mutation identifiers, all requested Tags and ancestors are revalidated immediately before creation, and this Tool never creates Tags. Immediately before a Project, Parent, or tagged call, restate the available target context and every full Tag path so the user can associate each canonical ID with the pending mutation; if any target is not distinguishable, do not call. Generate a fresh UUID idempotencyKey per new creation intent and reuse it only for a transparent retry. This server may return write_disabled without touching OmniFocus. Repeats, notifications, batches, edits, moves, reparenting, completion, deletion, fallback to Inbox/Project, silent Tag omission, and automatic Tag creation are unsupported.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
noteNo
tagIdsNo1-5 unique canonical IDs of existing OmniFocus Tags; names, paths, and automatic Tag creation are not accepted.
dueDateNo
flaggedNo
deferDateNo
destinationYes
plannedDateNo
idempotencyKeyYes
estimatedMinutesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
createdYes
successYes
warningsYes
idempotencyYes
Behavior5/5

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

Annotations set idempotentHint=true and destructiveHint=false; the description elaborates on idempotency key reuse, potential write_disabled error, and revalidation. No contradictions. Adds context about server behavior exceeding annotations.

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 relatively long but efficient; each sentence adds value. The first sentence immediately states the purpose. Could be slightly tighter but appropriate for the tool's complexity.

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 10 parameters, 3 required, and an output schema, the description covers purpose, preconditions, destination rules, unsupported features, and error behavior. It is complete for an agent to correctly select and invoke the 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 description coverage is low (10%), but the description compensates by thoroughly explaining the complex destination parameter, tagIds constraints, and idempotencyKey usage. Other params like note, flagged are not described, but the most critical ones are well covered.

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 'Create' and the resource 'OmniFocus task' with the qualifier 'after an explicit user request'. It distinguishes from sibling tools which are all read-only or search operations.

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 when-to-use (explicit user request), what destinations are valid (inbox, project ID, action group ID), what is not accepted (names, paths), prerequisites (fresh reads), and unsupported operations. Even instructs the agent to restate context before calling.

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/GlassyWorld/Omnifocus-Agent-MCP'

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