Skip to main content
Glama

filter_tasks

Read-only

Find TickTick tasks by project, date range, priority, tags, or status to build agendas and answer due-date queries. Results are capped at 200 tasks.

Instructions

Find TickTick tasks by project, date range, priority, tags or status. Use this for agendas and due-date queries; results are capped at 200.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "filter_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoTasks must contain all of these tags.
limitNo
statusNoWhich task statuses to return: open, completed, or both.open
endDateNoOnly tasks starting on or before this date.
priorityNoMatch any of these priorities.
startDateNoOnly tasks starting on or after this date.
projectIdsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful disclosure that results are capped at 200, but says nothing about ordering, what happens when no filters are supplied, or whether the cap truncates silently.

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?

Two short sentences with zero filler: the capability is front-loaded and the usage hint plus the result cap follow immediately. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and seven optional parameters, the description should say what an unfiltered call returns (all tasks? across all projects?) and how the default limit of 100 interacts with the 200 cap. It covers the main filtering story but leaves those invocation-shaping questions unanswered.

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 71%, so the schema carries most parameter meaning (enums, defaults, min/max, tag matching semantics). The description restates the filter axes and explains the 200 ceiling, which partially covers the undocumented 'limit' and 'projectIds' params, but adds no syntax or format detail for dates or project IDs.

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?

States a specific verb and resource ('Find TickTick tasks') plus the filter dimensions it supports (project, date range, priority, tags, status). An agent can tell it retrieves tasks, though it does not explicitly contrast itself with the similar-sounding siblings 'list_tasks' and 'search_tasks'.

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?

'Use this for agendas and due-date queries' gives a concrete positive use context, which is more than most search tools offer. It lacks any when-not guidance or routing to the overlapping siblings 'list_tasks'/'search_tasks', so an agent must still guess between near-duplicate tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.