Skip to main content
Glama

search_tasks

Read-only

Search TickTick tasks by keyword and filter by project, tag, status, or due date to find relevant tasks quickly.

Instructions

Search TickTick tasks by keyword, with optional project, tag, status and due-date filters. Results are capped at 200.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keywords": "<keywords>"
    },
    "name": "search_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
dueToNoOnly tasks due on or before this date.
limitNo
statusNoWhich task statuses to return: open, completed, or both.open
dueFromNoOnly tasks due on or after this date.
keywordsYesWords to search for in task titles and content.
projectIdsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description contributes the 200-result cap, which is meaningful behavioral context, but says nothing about whether results are paginated, ordered, or truncated silently. With annotations carrying safety, a 3 is appropriate.

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?

Two sentences, front-loaded with the primary action and scope. The 200-result cap restates the schema's `limit` maximum of 200, so that clause is partially redundant, though it usefully flags truncation as a behavior rather than a parameter constraint.

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?

For a seven-parameter search tool with no output schema, the description covers the surface but omits match semantics for array filters, date format expectations, and any note about result ordering or truncation beyond the cap. Adequate to call correctly, not complete enough to predict results confidently.

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?

Description enumerates the filter dimensions (project, tag, status, due date) that correspond to the seven params, giving an agent a mental model beyond the 57% schema coverage. It still does not clarify whether multiple `tags` or `projectIds` are ANDed or ORed, or the expected date format for dueFrom/dueTo.

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?

Names a specific verb and resource ("Search TickTick tasks") plus the scoping dimensions (project, tag, status, due date), which distinguishes it from a plain list or filter tool. It does not explicitly name a sibling alternative, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the requirement of `keywords`: this is the tool for text-based lookup rather than enumeration. However, it never states when to prefer it over filter_tasks or list_tasks, nor what to do when a search returns nothing or when keyword-free filtering is needed.

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