Skip to main content
Glama

task_reclassify

Reclassify multiple tasks at once by predicate matching, with a safe two-phase dry-run then apply process. Supports adding or removing tags, setting project, or flagging tasks uniformly.

Instructions

Predicate-driven bulk task reclassification with a mandatory two-phase contract. Phase 1 (dryRun: true): match tasks by predicate, return { matched, proposed: [{taskId, before, after}] } with no mutations. Phase 2 (dryRun: false): require confirmation echoing the matched count from the prior dry-run; mismatch fails fast. Caps at 200 matches per apply; use task_batch_update with explicit IDs for larger sets. Predicate AST: title-contains / tag / project leaves and and / or / not combinators (full shape in JSONSchema). Changes apply uniformly: addTags, removeTags, setProject, setFlagged. Do NOT use this tool when you have explicit task IDs — call task_batch_update directly. Side effects (apply phase only): writes to OmniFocus, sets meta.syncPending = true. Call sync_trigger when you need changes to appear on other devices. Example: task_reclassify({ predicate: { kind: "tag", tagId: "tag123" }, changes: { setFlagged: true }, dryRun: false, confirmation: "3" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNoDefault true — return the diff without mutating. false requires `confirmation` echoing the matched count from a prior dry-run.
changesYesChanges applied uniformly to every matched task.
predicateYesAST for selecting tasks. Composable via and/or/not. Always evaluated against open (non-completed, non-dropped) tasks.
confirmationNoWhen dryRun is false, the matched count from the most recent dry-run, as a string (e.g. "42"). Mismatch with the actual current match count fails the call fast.
Behavior5/5

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

Discloses side effects (writes to OmniFocus, sets syncPending), requires sync_trigger for visibility, explains dry-run vs apply phases, and failure conditions like confirmation mismatch. No annotations present, so description carries full burden.

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?

Description is a single well-structured paragraph covering all key topics. While thorough, it is somewhat lengthy but front-loaded with essential concepts. Every 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?

Given complex predicate AST, two-phase protocol, and no output schema, the description completely covers input constraints, behavior, side effects, exclusions, and provides an example. Agent has sufficient information 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?

Schema coverage is 100%, so baseline 3. Description adds context by explaining the dry-run default, confirmation echoing requirement, and predicate AST structure, enhancing understanding beyond schema descriptions.

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 the tool's purpose as 'Predicate-driven bulk task reclassification' with a two-phase contract. It distinguishes itself from sibling tools like task_batch_update by explicitly saying not to use it when explicit task IDs are known.

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?

Provides explicit guidance on when to use (predicates, bulk) and when not to (explicit IDs), with direct alternative (task_batch_update). Also explains the two-phase contract, match cap, and confirmation requirement.

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