Skip to main content
Glama

omnifocus_read

Read-onlyIdempotent

Query OmniFocus tasks, projects, tags, and more using flexible filters, modes for common views (today, overdue, flagged), and control over fields, sorting, and counts.

Instructions

Query OmniFocus data with flexible filtering. Returns tasks, projects, tags, perspectives, folders, or exports.

COMMON QUERIES:

  • Inbox: { query: { type: "tasks", filters: { project: null } } }

  • Tasks in a specific project (by ID, fast): { query: { type: "tasks", filters: { projectId: "" } } }

  • Overdue: { query: { type: "tasks", mode: "overdue" } }

  • Today perspective: { query: { type: "tasks", mode: "today" } }

  • Flagged: { query: { type: "tasks", mode: "flagged" } }

  • Upcoming (7 days): { query: { type: "tasks", mode: "upcoming", daysAhead: 7 } }

  • Smart suggestions: { query: { type: "tasks", mode: "smart_suggest", limit: 10 } }

  • Count only (fast): { query: { type: "tasks", filters: { flagged: true }, countOnly: true } }

  • Export tasks: { query: { type: "export", exportType: "tasks", format: "json" } }

MODES (tasks queries ONLY — not valid on type:"projects"):

  • today: Due soon (≤3 days) OR flagged, matching OmniFocus Today perspective

  • overdue: Tasks past their due date

  • flagged: Flagged tasks

  • upcoming: Tasks due in next N days (set daysAhead, default 14)

  • inbox, available, blocked, search, smart_suggest, all

  • To SEARCH projects (or tasks) use filters, not mode: filters: { name: { contains: "..." } } or filters: { text: { matches: "regex" } }

FILTER OPERATORS:

  • tags: { any: [...] } (has any), { all: [...] } (has all), { none: [...] } (has none)

  • dates (dueDate, deferDate, plannedDate, added): { before: "YYYY-MM-DD" }, { after: "..." }, { between: ["...", "..."] }

  • text: { contains: "..." }, { matches: "regex" }

  • boolean: flagged, blocked, available, inInbox

  • logic: { OR: [...] }, { AND: [...] }, { NOT: {...} }

RESPONSE CONTROL:

  • Default returns minimal fields (id, name, flagged, completed, dueDate, deferDate, tags, project, available)

  • details: true returns all fields with full notes

  • fields: [...] returns exactly those fields (note truncated to 200 chars unless details: true)

  • ID lookup always returns all fields with full notes

  • fields are type-specific; requesting a field of the other type (e.g. reviewInterval on tasks) returns a guided error

  • fields (tasks): id, name, completed, flagged, blocked, available, estimatedMinutes, dueDate, deferDate, plannedDate, completionDate, added, modified, dropDate, note, projectId, project, tags, repetitionRule, parentTaskId, parentTaskName, inInbox

  • fields (projects): id, name, status, flagged, note, dueDate, deferDate, completionDate, folder, folderPath, folderId, sequential, lastReviewDate, nextReviewDate, reviewInterval, defaultSingletonActionHolder, tags, plannedDate

  • sort: [{ field: "dueDate", direction: "asc" }]

  • limit/offset: Pagination (default limit: 25, max: 500)

  • countOnly: true returns only count (33x faster for "how many" questions) — tasks only

COMPLETED TASKS:

  • Use filters: { completed: true } or filters: { status: "completed" } to query completed tasks

  • includeCompleted is for export operations only (type: "export"); honored by exportType: "tasks" and exportType: "all"

EXPORT TO DISK:

  • outputDirectory: when set with exportType: "tasks", writes tasks. to disk (raises the implicit cap to 5000); required for exportType: "all"

  • A response-path export (no outputDirectory) caps at 1000 by default and emits summary.truncated when the cap fires; override with limit

PERFORMANCE:

  • Use countOnly for counting questions

  • Use fields to select only needed data

  • Use modes instead of raw filters when available

  • Default queries are token-efficient (9 fields, no notes)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds context: default fields, ID lookup returns full details, performance notes, and export behavior. No contradiction.

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 long but well-structured with sections and examples. It is front-loaded with a clear summary. A minor reduction for length, but each section earns its place given 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?

Highly complete: covers all aspects of usage including response control, pagination, performance, export details, and field lists. No output schema, but description sufficiently describes return behavior.

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

Parameters5/5

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

Schema has 0% description coverage, but the description explains every parameter in detail: types, modes, filters, fields, sort, limit, countOnly, etc. It adds immense value beyond the raw schema.

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 it queries OmniFocus data with flexible filtering, lists supported types (tasks, projects, tags, etc.), and distinguishes itself from sibling tools (omnifocus_write, omnifocus_analyze) by being read-only.

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 extensive, explicit guidance: common queries, modes (with constraints like 'tasks queries ONLY'), filter operators, response control, performance tips, and caveats (e.g., includeCompleted only for export). Clearly differentiates when to use modes vs filters.

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/kip-d/omnifocus-mcp'

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