Skip to main content
Glama

list_tasks

Read-only

Retrieve TickTick tasks with optional project or inbox filtering and open, completed, or all status selection, returning up to 200 results.

Instructions

List TickTick tasks, optionally limited to one project or "inbox". Status can be open, completed or all; 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": "list_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNoWhich task statuses to return: open, completed, or both.open
projectIdNoProject ID, or "inbox". Omit to search all accessible projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false), so the description is not obligated to cover safety. It does add real behavioral context: the valid status values and the hard result cap of 200. It stops short of saying what happens past 200 (truncation vs. an error) or how to retrieve more, which is the one remaining behavioral gap.

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 clauses, zero filler, and the resource plus scope is front-loaded before the status enumeration and the cap. Every phrase carries information an agent needs to call it correctly.

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 simple zero-required-parameter read tool this is close to adequate, but with no output schema the description never indicates what a task record contains, and the truncation-at-200 behavior is stated without describing the consequence. It also leaves the sibling-selection question open in a catalog dense with task-listing alternatives.

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 67%: status and projectId carry inline descriptions, while limit is documented only by default=100 / maximum=200. The description reinforces the cap and the project scoping but adds little meaning beyond the schema, notably not explaining how limit interacts with the 200 result cap.

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 opens with a specific verb and resource ("List TickTick tasks") and states the scoping options (single project or "inbox") plus the status dimension. It does not name or differentiate from sibling lookalikes such as filter_tasks, search_tasks, or the get_* tools, so an agent must infer the boundary itself.

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 only implied: you call it to enumerate tasks, optionally narrowed by project or status. There is no statement of when this is preferable to filter_tasks or search_tasks, nor any exclusion such as a note that this is not for keyword queries. The "inbox" special value is the only routing hint offered.

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