Skip to main content
Glama
estrenuo

OmniFocus MCP Server

by estrenuo

Get Perspective Tasks

omnifocus_get_perspective_tasks
Read-onlyIdempotent

Retrieve tasks from a specific OmniFocus perspective. Provide the perspective name to get its task list, with an optional limit on the number of tasks returned.

Instructions

Get tasks shown in a specific OmniFocus perspective.

Switches the front OmniFocus window to the named perspective, reads the tasks it displays, then restores the original perspective.

Args:

  • perspectiveName (string): Name of the perspective (use omnifocus_list_perspectives to find names)

  • limit (number): Maximum tasks to return, 1-500 (default: 50)

Returns: Array of task objects with: id, name, note, completed, flagged, dueDate, deferDate, projectName, tags, estimatedMinutes

Examples:

  • Get tasks from a perspective: { perspectiveName: "Next" }

  • With limit: { perspectiveName: "Forecast", limit: 10 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of tasks to return
perspectiveNameYesThe name of the perspective to get tasks from
Behavior4/5

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

Annotations (readOnlyHint, destructiveHint) already indicate safety. Description adds valuable behavioral context: switching the front window and restoring the original perspective, which is not captured by 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?

Description is front-loaded with purpose, followed by behavioral note, then clearly structured Args, Returns, and Examples. Every sentence earns its place without redundancy.

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?

Despite no output schema, description lists all return fields. It explains the window-switching side effect and restoration. Tool is simple but all necessary info is provided.

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 description adds value by suggesting how to find perspective names and providing examples with default limit, going beyond schema definitions.

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?

Description clearly states 'Get tasks shown in a specific OmniFocus perspective' and explains the switching/restoring behavior, distinguishing it from sibling tools like get_project_tasks or list_inbox.

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?

Provides guidance to use omnifocus_list_perspectives for finding perspective names and includes examples. While it doesn't explicitly exclude alternatives, the context makes it clear when to use this tool.

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