Skip to main content
Glama
estrenuo

OmniFocus MCP Server

by estrenuo

Create Folder

omnifocus_create_folder

Create a new folder in OmniFocus at the top level or nested inside an existing folder by specifying the folder name and an optional parent folder.

Instructions

Create a new folder in OmniFocus.

Creates a folder at the top level or nested inside an existing folder.

Args:

  • name (string): Folder name (required)

  • parentFolderName (string, optional): Parent folder to nest inside (top level if omitted)

Returns: The created folder object with id, name, and other properties

Examples:

  • Top-level folder: { name: "Work" }

  • Nested folder: { name: "Q1", parentFolderName: "Work" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFolder name (required)
parentFolderNameNoName of the parent folder to nest inside. If omitted, folder is created at the top level.
Behavior4/5

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

Annotations indicate destructiveHint=false and readOnlyHint=false, consistent with creating a folder (a non-destructive mutation). The description details the behavior (top-level vs nested) and indicates a return value, adding transparency beyond 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?

The description is concise and well-structured with a summary, parameter list, return value, and examples. Every sentence serves a purpose with no 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?

Given the simplicity of the tool (2 parameters, no output schema, basic annotations), the description fully covers the purpose, parameters, return value, and usage scenarios. No gaps remain.

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?

Since schema coverage is 100%, the baseline is 3. The description adds value with examples showing how to use name and parentFolderName, clarifying their roles beyond schema descriptions.

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 creates a folder in OmniFocus, distinguishing it from sibling tools like update_folder or delete_folder. It specifies top-level or nested creation, leaving no ambiguity.

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?

The description provides clear context for when to use the tool (creating a new folder) and includes examples for top-level and nested usage. It doesn't explicitly state when not to use, but the purpose is self-evident given the sibling tools.

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