Skip to main content
Glama

get_projects

Fetch projects from OmniFocus with filters for project ID, search query, status (flagged, on hold, completed, stalled), tags, due/defer/planned dates, task count, and health metrics. Include optional fields like notes and last activity.

Instructions

Retrieve projects with optional filtering.

Parameters:

  • project_id: str -- filter to specific project

  • query: str -- search name/note/folder (case-insensitive)

  • flagged_only, on_hold_only, completed_only: bool

  • stalled_only: bool -- active projects with no available next actions

  • include_dropped, include_completed: bool -- include hidden states

  • include_full_notes: bool

  • include_task_health: bool -- adds remainingCount, availableCount, overdueCount, deferredCount, stalled, health

  • include_last_activity: bool -- adds lastActivityDate

  • has_overdue_tasks: bool -- implies include_task_health

  • tag_filter: list[str] -- projects with ALL specified tags

  • due_after, due_before, due_on: str -- ISO date filters for due date

  • defer_after, defer_before, defer_on: str -- ISO date filters for defer date

  • planned_after, planned_before, planned_on: str

  • completion_after, completion_before, completion_on: str

  • dropped_after, dropped_before, dropped_on: str

  • created_after, created_before, created_on: str

  • modified_after, modified_before, modified_on: str

  • min_task_count: int

  • has_no_due_dates: bool

  • sort_by: str -- "name", "due_date", "defer_date", "planned_date", "creation_date", "modification_date", "completion_date", "dropped_date"; sort_order: str -- "asc"/"desc"

Returns: id, name, folderPath, status, projectType, sequential (deprecated), completedByChildren, flagged, creationDate, modificationDate, completionDate, droppedDate, dueDate, deferDate, plannedDate, tags, note, lastReviewDate, nextReviewDate, reviewIntervalValue, reviewIntervalUnit. Optional health/activity fields when requested.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNo
include_full_notesNo
on_hold_onlyNo
queryNo
include_task_healthNo
include_last_activityNo
stalled_onlyNo
flagged_onlyNo
include_droppedNo
include_completedNo
completed_onlyNo
tag_filterNo
planned_afterNo
planned_beforeNo
planned_onNo
due_afterNo
due_beforeNo
due_onNo
defer_afterNo
defer_beforeNo
defer_onNo
completion_afterNo
completion_beforeNo
completion_onNo
dropped_afterNo
dropped_beforeNo
dropped_onNo
created_afterNo
created_beforeNo
created_onNo
modified_onNo
has_overdue_tasksNo
sort_byNo
sort_orderNoasc
modified_afterNo
modified_beforeNo
min_task_countNo
has_no_due_datesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations are absent, so the description carries the burden. It explains parameter behaviors (e.g., stalled_only, has_overdue_tasks) but does not mention rate limits, pagination, or result size limits. The read-only nature is implied but not explicitly stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is thorough but verbose, spanning many lines. It is well-structured with parameter documentation and return field listing, but could be more concise by grouping similar date filters.

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?

Given the high parameter count and existence of an output schema, the description covers nearly all aspects of the tool, including all parameters and return fields. It lacks pagination info and error handling, but is otherwise comprehensive.

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?

With 0% schema description coverage, the description fully compensates by providing clear explanations for all 38 parameters, including types, defaults, and semantics (e.g., 'stalled_only: bool -- active projects with no available next actions').

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 the tool retrieves projects with optional filtering, using the verb 'Retrieve' and resource 'projects'. It distinguishes itself from sibling tools like create_projects, delete_projects, and update_projects by focusing on read-only retrieval.

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?

No explicit guidance on when to use this tool versus alternatives like get_tasks or get_focus. The description lacks context about prerequisites, exclusivity, or when not 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/s-morgan-jeffries/omnifocus-mcp'

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