Skip to main content
Glama

task_search

Search OmniFocus tasks by keyword or filters. Narrow results with project, tags, due dates, availability, and pagination.

Instructions

Search OmniFocus tasks by keyword and/or structured filters, with cursor pagination. q is optional — omit it to filter by tag, project, date range, or availability alone. When q is supplied, scans task names and/or notes (controlled by scope) for a case-insensitive substring match. Narrow results with: projectId, tagIds (task must carry ALL listed tags), available, dueBefore, dueAfter, flagged, and completed. At least one of q, projectId, tagIds, available, dueBefore, or dueAfter must be provided. Do NOT use when you already have an ID — prefer task_get instead. Returns tasks[] with pagination (limit defaults to 50, max 500); safe to call repeatedly; no side effects. Example: task_search({ q: "dentist" }) Example: task_search({ tagIds: ["tag123"], available: true, dueBefore: "2026-05-01T00:00:00Z" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch query. Case-insensitive substring match applied to the fields in scope. Optional — omit to filter by tags, project, date range, or availability alone.
limitNoMax results per page (1..500). Default 50. Use cursor to fetch subsequent pages.
scopeNo'name' = search task name only; 'note' = search note only; 'all' = both (default). Ignored when q is omitted.
cursorNoOpaque cursor from a previous task_search response. Must use the same filters — changing filters mid-sequence returns a ValidationError.
tagIdsNoRestrict to tasks carrying ALL of these tag IDs.
flaggedNotrue = flagged tasks only; false = unflagged only; omit = all.
dueAfterNoTasks with dueDate strictly after this moment. ISO-8601 with offset or relative shortcut.
availableNotrue = only tasks available to work on now (not blocked, not deferred, not completed). Omit = all.
completedNo'exclude' = active tasks only (default); 'only' = completed tasks only; 'any' = both.
dueBeforeNoTasks with dueDate strictly before this moment. ISO-8601 with offset or relative shortcut.
projectIdNoRestrict search to tasks within this project.
includeLinksNoWhen true, each task carries a `_links` HATEOAS block (self, project, parent, tags). Default false — the block is omitted to save payload size. Use the task's `id`, `projectId`, `parentId`, and `tagIds` fields directly instead.
Behavior5/5

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

Discloses side-effect-free nature ('safe to call repeatedly; no side effects'), pagination behavior, case-insensitive substring matching, and scope usage. No annotations provided, so description fully covers behavioral traits.

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?

Well-structured with purpose first, then filter details, examples. Slightly verbose but 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?

Covers search behavior, pagination, filters, constraints, and examples despite no output schema. Adequate for a 12-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds context beyond 100% schema-covered parameters: explains optionality of q, scope interaction, required filter combinations, and pagination defaults.

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?

Clear verb 'search', resource 'tasks', and distinguishes from sibling tool task_get: 'Do NOT use when you already have an ID — prefer task_get instead.'

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?

Explicit when to use (keyword and/or structured filters), when not (if ID known, use task_get), and required conditions: 'At least one of q, projectId, tagIds, available, dueBefore, or dueAfter must be 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/torsday/omnifocus-mcp'

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