Skip to main content
Glama

project_create

Add a new project to OmniFocus with custom settings for folder, tags, dates, and status.

Instructions

Create a new OmniFocus project. Optionally place it in a folder, assign tags, set completion criterion, status, defer/due dates, estimated minutes, flagged state, and review interval. Safety control: pass idempotency_key to make transport retries safe — identical subsequent calls within the TTL window replay the original envelope with meta.idempotentReplay = true instead of creating a duplicate project. Returns { created: true, id }. Side effects: creates a project in OmniFocus, sets meta.syncPending = true. Call sync_trigger when you need the project to appear on other devices. Example: project_create({ name: "Website Redesign" }) Example: project_create({ name: "Q3 Planning", folderId: "fld123", flagged: true })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name. Required, must be non-empty.
noteNoPlain-text note for the project.
statusNoInitial project status. Default: active. Accepts: 'paused' → on-hold.
tagIdsNoTag IDs to apply to the project.
dueDateNoDue date as ISO-8601 with UTC offset.
flaggedNoFlag the project.
folderIdNoFolder ID to place the project in. Omit for root.
deferDateNoDefer date as ISO-8601 with UTC offset.
dueDateFloatingNoWhen true, the due time is floating (follows the user across time zones).
idempotency_keyNoIdempotency key for retry-safe creates. Identical subsequent calls within the TTL window replay the original envelope with meta.idempotentReplay = true instead of creating a duplicate project.
estimatedMinutesNoEstimated total duration in minutes.
deferDateFloatingNoWhen true, the defer time is floating (follows the user across time zones).
reviewIntervalDaysNoReview interval in days. Omit to use OmniFocus default.
completionCriterionNoHow the project's tasks are completed: parallel (any order), sequential (in order), or singleActions. Accepts: 'in-order' → sequential, 'in order' → sequential, 'any-order' → parallel, 'any order' → parallel.
Behavior4/5

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

The description discloses side effects (creates a project, sets syncPending), idempotency behavior with key, and the need to call sync_trigger for multi-device sync. With no annotations, this provides valuable behavioral context beyond the action itself.

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 concise given the 14 parameters. It front-loads the core purpose, then lists parameters efficiently. Examples are provided. However, it could be trimmed slightly by removing redundant phrases like 'Optionally place it in a folder' since the parameter list covers it.

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?

For a 14-parameter creation tool with no output schema, the description covers return format, idempotency, side effects, and follows up with sync guidance. The examples illustrate typical use cases. Minor gap: it does not clarify that the tool may fail if the folderId is invalid, but overall complete enough.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all parameters. The description adds limited value by explaining idempotency_key's purpose and providing aliases for status and completionCriterion. The examples are helpful but don't substantially deepen parameter understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Create a new OmniFocus project' with a specific verb and resource. It lists optional placement, tags, dates, etc., making the purpose unambiguous. However, it does not differentiate from sibling tools like project_create_describe, which is a dry-run variant.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention when not to use it, nor does it compare to project_create_describe, project_batch_complete, or other creation-related 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/torsday/omnifocus-mcp'

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