Skip to main content
Glama

folder_delete_describe

Preview the effects of deleting an OmniFocus folder without making changes. Returns a description and planned changes to review before actual deletion.

Instructions

Preview what folder_delete would do without making any changes. Do NOT use to actually delete a folder — use folder_delete instead. Returns { description, plannedChanges } describing the deletion that would occur. No side effects: read-only by contract — never mutates OmniFocus. Example: dry-run companion — pass the same args you would to the write tool, inspect plannedChanges, then call the write tool once approved.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPersistent folder ID to delete. Get from folder_list.
cascadeNoWhen true, orphan all direct projects and recursively delete subfolders before deleting. Default false — returns an error if the folder is non-empty.
Behavior5/5

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

Explicitly states 'No side effects: read-only by contract' and 'never mutates OmniFocus'. With no annotations, description fully discloses behavior.

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?

Three sentences, front-loads key purpose, no fluff. Each sentence adds value.

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?

Covers purpose, usage, behavior, return value (description and plannedChanges), and relationship to sibling. No output schema, but description compensates.

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?

Schema coverage is 100%, so baseline is 3. Description mentions 'pass the same args' but does not elaborate on individual parameters beyond 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?

Description clearly states it previews folder deletion without changes, distinguishing from folder_delete. Uses 'preview', 'dry-run', and explicitly says 'Do NOT use to actually delete'.

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?

Explicitly instructs when to use (dry-run) and when not (actual deletion), directing to folder_delete instead. Provides clear example of workflow.

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

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