Skip to main content
Glama

edit_item

Destructive

Modify any OmniFocus task or project by changing its name, note, status, dates, tags, or relocating it to another project or folder.

Instructions

Edit a task or project in OmniFocus

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe ID of the task or project to edit
nameNoThe name of the task or project to edit (as fallback if ID not provided)
addTagsNoTags to add to the task
newNameNoNew name for the item
newNoteNoNew note for the item
itemTypeYesType of item to edit ('task' or 'project')
newStatusNoNew status for tasks (incomplete, completed, dropped)
newDueDateNoNew due date in ISO format (YYYY-MM-DD or full ISO date); set to empty string to clear
newFlaggedNoSet flagged status (set to false for no flag, true for flag)
removeTagsNoTags to remove from the task
moveToInboxNoFor tasks: move task to inbox
replaceTagsNoTags to replace all existing tags with
newDeferDateNoNew defer date in ISO format (YYYY-MM-DD or full ISO date); set to empty string to clear
newProjectIdNoFor tasks: move task to this project ID
exclusiveTagsNoRespect mutually exclusive tag groups when adding/replacing tags (default: true). When a tag belongs to an exclusive group, sibling tags from that group are removed.
newFolderNameNoNew folder to move the project to
newSequentialNoWhether the project should be sequential
newPlannedDateNoNew planned date in ISO format (YYYY-MM-DD or full ISO date); set to empty string to clear
newProjectNameNoFor tasks: move task to this project name (errors on duplicate names)
newParentTaskIdNoFor tasks: move task under this parent task ID
newProjectStatusNoNew status for projects
newParentTaskNameNoFor tasks: move task under this parent task name (errors on duplicate names)
newEstimatedMinutesNoNew estimated minutes
Behavior2/5

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

The description only says 'Edit', which matches the destructiveHint=true annotation, but provides no additional behavioral details (e.g., that it can modify multiple fields, move items, or change status). The burden falls on annotations, but the description adds almost no value beyond them.

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

Conciseness4/5

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

The description is a single concise sentence, front-loading the core purpose. However, it is so brief that it may omit necessary context for a tool with 23 parameters, making it slightly underspecified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (23 parameters, no output schema, limited annotations), the description is insufficient. It fails to summarize the scope of editable fields, the side effects of edits, or any constraints. The agent must rely entirely on the schema for operational context.

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 description coverage is 100%, so the baseline is 3. The description adds no further meaning beyond the schema; it merely restates that the tool edits tasks or projects. No parameter-specific elaboration is provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Edit' and the resource 'task or project in OmniFocus', providing a specific purpose. However, it does not differentiate from sibling tools like edit_folder or edit_tag, which may cause confusion.

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?

The description offers no guidance on when to use this tool versus alternatives such as add_omnifocus_task, add_project, or other mutation tools. No when-to-use or when-not-to-use information is provided.

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

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