delete_task
Remove a task permanently from your OmniFocus project by providing its ID.
Instructions
Permanently delete a task from OmniFocus
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The task ID to delete |
Remove a task permanently from your OmniFocus project by providing its ID.
Permanently delete a task from OmniFocus
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The task ID to delete |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description reveals that deletion is permanent, which is a key behavioral trait. However, with no annotations, it lacks details on side effects, permissions, or state requirements.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, focused sentence with no unnecessary words, effectively conveying the core action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple delete operation with one parameter, the description is mostly sufficient. It could note that it only deletes a single task, distinguishing from batch operations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 100% coverage for the single parameter 'id' with a description. The tool description adds no additional meaning beyond that.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it permanently deletes a task from OmniFocus, using a specific verb and resource. It distinguishes itself from siblings like batch_delete_tasks by focusing on single task deletion.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like batch_delete_tasks. The description does not mention prerequisites or scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/IllyaStarikov/omnifocus-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server