Skip to main content
Glama
Sign In
OmniFocus MCP Server

OmniFocus MCP Server

by estrenuo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Folders

omnifocus_list_folders
Read-onlyIdempotent

List folders in OmniFocus to view hierarchical project organization. Filter by status (active, dropped, all) and limit results.

Instructions

List folders in OmniFocus.

Folders are used to organize projects hierarchically.

Args:

  • status (string): Filter by status - 'all', 'active', 'dropped' (default: 'active')

  • limit (number): Maximum folders to return, 1-200 (default: 50)

Returns: Array of folder objects with: id, name, status, projectCount, folderCount, parentName

Examples:

  • List active folders: {}

  • List all folders: { status: "all" }

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "omnifocus_list_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of folders to return
statusNoFilter by folder statusactive

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint true and destructiveHint false. The description adds value by detailing return fields (id, name, status, projectCount, folderCount, parentName) and examples, beyond what annotations provide.

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?

The description is concise with three short paragraphs (overview, args, returns) plus examples. Every sentence is informative and well-structured, front-loading the core purpose.

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 lacking an output schema, the description fully explains the return array structure with field names. It covers all necessary information for a list tool: purpose, arguments with defaults, and return format.

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?

Input schema has 100% coverage with descriptions for both parameters. The description repeats this info and adds examples, but does not significantly extend meaning beyond the schema. Baseline 3 is appropriate.

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 'List folders in OmniFocus' and explains that folders organize projects hierarchically. It distinguishes itself from sibling list tools (e.g., omnifocus_list_projects) by focusing specifically on folders.

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

Usage Guidelines3/5

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

The description provides examples and defaults but does not explicitly state when to use this tool versus alternatives like omnifocus_list_projects or omnifocus_search. Usage context is implied but lacks explicit when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools