Skip to main content
Glama
estrenuo

OmniFocus MCP Server

by estrenuo

Create Project

omnifocus_create_project

Create a new project in OmniFocus with optional due dates, defer dates, flags, sequential ordering, and folder placement.

Instructions

Create a new project in OmniFocus.

Creates a project at the top level or inside a specific folder. Optional properties like due date, defer date, flags, and sequential ordering can be set.

Args:

  • name (string): Project name (required)

  • note (string): Optional note/description

  • folderName (string): Folder to place the project in (top level if omitted)

  • dueDate (string): Due date in ISO 8601 format

  • deferDate (string): Defer/start date in ISO 8601 format

  • flagged (boolean): Flag the project (default: false)

  • sequential (boolean): Tasks must be done in order (default: false = parallel)

  • status (string): "active", "on hold", "done", or "dropped" (default: "active")

Returns: The created project object with id, name, and other properties

Examples:

  • Simple project: { name: "Launch website" }

  • In a folder: { name: "Q1 Planning", folderName: "Work" }

  • With details: { name: "Write book", dueDate: "2024-12-31T17:00:00", sequential: true, flagged: true }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name (required)
noteNoOptional note/description for the project
statusNoInitial project statusactive
dueDateNoDue date in ISO 8601 format
flaggedNoWhether to flag the project
deferDateNoDefer/start date in ISO 8601 format
folderNameNoName of the folder to place the project in. If omitted, project is created at the top level.
sequentialNoIf true, tasks must be completed in order (sequential project). Default is parallel.
Behavior4/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, which align with the creation behavior. The description adds value by explaining folder nesting and default status, though it doesn't detail side effects like overwriting or required permissions. No contradictions with annotations.

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?

The description is well-structured with sections for Args, Returns, and Examples. Every sentence serves a purpose, with no redundancy or fluff. It is concise yet comprehensive.

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?

With 8 parameters and no output schema, the description thoroughly explains each parameter and provides example usage. The return value is summarized, sufficient for a creation tool. The context (annotations, schema coverage) is fully leveraged.

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%, but the description adds meaningful context beyond the schema, such as mentioning ISO 8601 date formats, default values for flagged/sequential/status, and providing examples. This aids the agent in correctly formatting parameters.

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 explicitly states 'Create a new project in OmniFocus' and specifies top-level or folder placement, clearly distinguishing it from sibling tools like omnifocus_create_task, omnifocus_create_folder, and omnifocus_update_project.

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 clearly indicates when to use this tool (creating a project) and outlines optional properties. However, it lacks explicit guidance on when not to use it compared to alternatives like omnifocus_update_project, but the context of sibling names and the action verb provide adequate direction.

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