Skip to main content
Glama
estrenuo

OmniFocus MCP Server

by estrenuo

Mark Project Reviewed

omnifocus_mark_project_reviewed

Mark a project as reviewed by providing its ID or name. The next review date is set based on the project's existing interval or a custom interval you specify.

Instructions

Mark a project as reviewed and update its next review date.

Use either the project ID or project name to identify the project. The next review date will be set based on the project's review interval or a custom interval if provided.

Args:

  • projectId (string, optional): The project's ID. Takes priority if both projectId and projectName provided.

  • projectName (string, optional): The project's name to search for. At least one of projectId or projectName is required.

  • reviewIntervalDays (number, optional): Custom review interval in days (1-3650). If not provided, uses the project's current review interval.

Returns: The updated project object

Examples:

  • By ID: { projectId: "abc123" }

  • By name: { projectName: "Work Project" }

  • With custom interval: { projectName: "Weekly Project", reviewIntervalDays: 7 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdNoThe project ID to mark as reviewed. Takes priority if both projectId and projectName are provided.
projectNameNoThe project name to search for. Used if projectId is not provided.
reviewIntervalDaysNoNumber of days until next review (optional - uses project's current interval if not specified)
Behavior4/5

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

Annotations indicate mutability (readOnlyHint: false). The description adds that the next review date is set based on the project's review interval or a custom interval. No contradictions found.

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, well-structured with Args and Examples sections. Every sentence adds value without 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?

Despite no output schema, the description mentions the return value (updated project object). All parameters are well-documented, and examples cover common use cases. Sufficient for an agent to use correctly.

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?

With 100% schema coverage, the baseline is 3. The description adds value by clarifying the priority of projectId over projectName and explaining reviewIntervalDays defaults. Examples further illustrate usage.

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 'Mark a project as reviewed and update its next review date', with a specific verb and resource. It distinguishes from sibling tools like omnifocus_batch_mark_reviewed by being single-project.

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 explains when to use projectId vs projectName and provides examples. It implicitly says to use this for single projects vs batch. However, it doesn't explicitly mention when not to use or list alternatives.

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