Skip to main content
Glama

project_update

Update specific fields of an existing OmniFocus project while leaving others unchanged. Supports clearing fields by passing null, with safety controls like dry run and conflict detection.

Instructions

Partially update mutable fields on an OmniFocus project. Only supplied fields are changed; omit a field to leave it unchanged. Pass null for note, deferDate, dueDate, estimatedMinutes, or reviewIntervalDays to clear those fields. Do NOT use to create or delete projects; prefer project_create or project_delete instead. Safety controls: set dry_run=true to preview without mutating; pass expectedModifiedAt (from a recent project_get) to reject the call if the project changed since you read it; pass idempotency_key to coalesce retries so the same update is only performed once. Returns { updated: true, id, name } — name reflects the post-patch name. Side effects: writes to OmniFocus, sets meta.syncPending = true. Call sync_trigger when you need changes to appear on other devices. Example: project_update({ id: "prj123", name: "New Name", flagged: true }) Example: project_update({ id: "prj123", status: "on-hold", dry_run: true })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPersistent project ID. Get from project_list or project_get.
nameNoNew project name. Must be non-empty if supplied.
noteNoPlain-text note. Pass null to clear.
statusNoProject status. Use project_complete or project_drop to close a project. Accepts: 'paused' → on-hold.
tagIdsNoFull-replacement tag list. Replaces all existing tags.
dry_runNoWhen true, validates input and returns a preview envelope with meta.dryRun = true; no adapter call is made and no mutation occurs.
dueDateNoISO-8601 due date with UTC offset. Pass null to clear.
flaggedNoFlag or unflag the project.
noteHtmlNoHTML note. Pass null to clear. Prefer note for plain-text edits.
deferDateNoISO-8601 defer date with UTC offset. Pass null to clear.
dueDateFloatingNoWhen true, the due time is floating (follows the user across time zones).
idempotency_keyNoIdempotency key for retry-safe updates. Identical subsequent calls within the TTL window replay the original envelope with meta.idempotentReplay = true instead of re-applying the patch.
estimatedMinutesNoEstimated total duration in minutes. Pass null to clear.
deferDateFloatingNoWhen true, the defer time is floating (follows the user across time zones).
expectedModifiedAtNoOptimistic-concurrency guard: ISO-8601 timestamp from a recent project_get. If the project's current modifiedAt differs, the call fails with OF_CONFLICT and no update is performed. Omit to skip the check.
reviewIntervalDaysNoReview interval in days. Pass null to clear.
completionCriterionNoHow the project's tasks are completed. Accepts: 'in-order' → sequential, 'in order' → sequential, 'any-order' → parallel, 'any order' → parallel.
Behavior5/5

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

No annotations are provided, so the description fully covers behavioral traits: it details that only supplied fields are changed, null clears specific fields, side effects include writing to OmniFocus and setting meta.syncPending, and the return value includes updated status. It also explains concurrency guard via expectedModifiedAt and idempotency via idempotency_key.

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 well-structured, starting with the main purpose, then clearing mechanism, usage restrictions, safety controls, return value, and examples. It is front-loaded with key information. While slightly long, every sentence contributes value; minor redundancy could be trimmed.

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 the high parameter count (17) and no output schema, the description is thorough: it covers update mechanics, safety controls, side effects, return value structure, and references sibling tools for other operations. It also explains concurrency and idempotency, making the tool's behavior fully understandable.

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 100%, so baseline is 3. The description adds value beyond the schema by explaining how to clear fields (pass null), aliases for status ('paused' → on-hold), and preference for note over noteHtml. It also provides examples that clarify parameter usage.

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 identifies the tool as 'Partially update mutable fields on an OmniFocus project' and distinguishes it from creation/deletion tools by explicitly stating 'Do NOT use to create or delete projects; prefer project_create or project_delete instead.' The verb 'update' combined with the resource 'project' is specific and unambiguous.

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?

The description provides explicit guidance on when to use the tool (partial updates) and when not to (create/delete), with named alternatives. It also explains safety controls like dry_run and expectedModifiedAt, giving clear context for correct invocation in different scenarios.

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