Skip to main content
Glama
IllyaStarikov

OmniFocus MCP Server

create_tag

Add a new tag to organize tasks. Optionally nest under a parent tag, set whether it allows next actions, or change its status.

Instructions

Create a new tag in OmniFocus

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesTag name
parentTagIdNoParent tag ID for nested tags
parentTagNameNoParent tag name for nested tags
allowsNextActionNoWhether tasks with this tag can be next actions (default true)
statusNoTag status
Behavior2/5

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

No annotations exist, so the description must convey behavioral traits. It does not mention uniqueness constraints, side effects, or requirements (e.g., tag name uniqueness). The schema covers parameters but not behavior.

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 extremely concise with no wasted words. However, it could be slightly more informative without losing conciseness.

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 5 parameters and no output schema or annotations, the description is insufficient. It lacks information about return values, error conditions, and prerequisites for a creation tool.

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. The description adds no extra meaning over the schema; it simply states the action without clarifying parameter relationships or semantics.

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 is clear and specific: 'Create a new tag in OmniFocus' uses a precise verb and resource, making the action immediately understandable.

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?

No guidance is provided on when to use this tool versus alternatives like update_tag or list_tags. The sibling list exists but is not referenced.

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

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