Skip to main content
Glama

filter_tasks

Read-onlyIdempotent

Filter OmniFocus tasks by status, dates, projects, tags, search, and more, with optional subtask tree expansion.

Instructions

Advanced task filtering by status, dates, projects, tags, search, and more, with optional subtask-tree expansion

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of tasks to return (default: 100)
cursorNoOpaque continuation cursor returned by a previous filter_tasks page
sortByNoSort results by field
flaggedNoFilter by flagged status
hasNoteNoFilter tasks that have notes
inInboxNoFilter tasks in inbox
overdueNoShow overdue tasks only
dueAfterNoShow tasks due strictly after this date/time (ISO format: YYYY-MM-DD or full ISO)
dueTodayNoShow tasks due today
dueBeforeNoShow tasks due strictly before this date/time (ISO format: YYYY-MM-DD or full ISO)
sortOrderNoSort order (default: asc)
tagFilterNoFilter by tag name(s). Can be single tag or array of tags
deferAfterNoShow tasks with defer date strictly after this date/time (ISO format: YYYY-MM-DD or full ISO)
deferTodayNoShow tasks deferred to today
outputModeNoOutput detail: detailed (default) or compact for broad planning queries
searchTextNoSearch in task names and notes
taskStatusNoFilter by task status. Can specify multiple statuses
deferBeforeNoShow tasks with defer date strictly before this date/time (ISO format: YYYY-MM-DD or full ISO)
dueThisWeekNoShow tasks due this week
estimateMaxNoMaximum estimated minutes
estimateMinNoMinimum estimated minutes
hasEstimateNoFilter tasks that have time estimates
perspectiveNoLimit search to specific perspective: inbox, flagged, all tasks
dueThisMonthNoShow tasks due this month
plannedAfterNoShow tasks planned strictly after this date/time (ISO format: YYYY-MM-DD or full ISO)
plannedTodayNoShow tasks planned for today
showSubtasksNoExpand each matching task's subtask tree (default: false)
deferThisWeekNoShow tasks deferred to this week
exactTagMatchNoSet to true for exact tag name match, false for partial (default: false)
plannedBeforeNoShow tasks planned strictly before this date/time (ISO format: YYYY-MM-DD or full ISO)
projectFilterNoFilter by project name (partial match)
completedAfterNoShow tasks completed strictly after this date/time (ISO format: YYYY-MM-DD or full ISO)
completedTodayNoShow tasks completed today
deferAvailableNoShow tasks whose defer date has passed (now available)
completedBeforeNoShow tasks completed strictly before this date/time (ISO format: YYYY-MM-DD or full ISO)
maxSubtaskDepthNoMaximum subtask levels to expand; omitted means unlimited
plannedThisWeekNoShow tasks planned for this week
plannedThisMonthNoShow tasks planned for this month
completedThisWeekNoShow tasks completed this week
completedThisMonthNoShow tasks completed this month
Behavior3/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, covering safety. Description adds 'optional subtask-tree expansion' but that's already in schema. Provides no additional behavioral context beyond annotations.

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?

Single sentence, front-loaded with key purpose, no unnecessary words. Efficiently conveys the tool's scope without verbosity.

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?

With 40 parameters and no output schema, the description is insufficient. It doesn't mention pagination (cursor/limit) or output format. Lacks context about how results are returned despite high schema coverage.

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 baseline is 3. Description provides a high-level summary ('by status, dates, projects, tags, search') but adds no new meaning beyond what each parameter's description already provides.

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 it is for 'Advanced task filtering' by multiple criteria and mentions subtask-tree expansion. However, it does not explicitly differentiate from sibling tools like get_inbox_tasks or get_flagged_tasks, though 'advanced' implies broader scope.

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 on when to use this tool versus alternatives. Sibling tools exist for specific filters (e.g., get_inbox_tasks) but description doesn't mention when to choose those instead.

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