Skip to main content
Glama
evalor
by evalor

List Tasks

list_tasks

List and filter uncompleted tasks from Dida365 by project, priority, date range, or quick presets like today, tomorrow, this week, or overdue.

Instructions

List and filter tasks (任务) across one or more projects (清单).

WHEN TO USE:

  • Find tasks due today (今天的任务), this week (本周任务), or overdue (逾期任务)

  • Filter tasks by priority (优先级) or date range (日期范围)

  • Search tasks across multiple projects (清单) or inbox (收集箱)

  • Get a filtered subset of tasks

WHEN NOT TO USE:

  • Need all tasks in one project without filtering → use 'get_project_data'

  • Need a single specific task → use 'get_task'

QUICK FILTERS (preset 快速筛选):

  • "today": Tasks due today (今天的任务)

  • "tomorrow": Tasks due tomorrow (明天的任务)

  • "thisWeek": Tasks due this week (本周任务)

  • "overdue": Past-due tasks (逾期任务)

OPTIONAL FILTERS:

  • projectId: Single ID, array of IDs, or "inbox" (收集箱) (omit for all projects/所有清单)

  • dueDateFrom/dueDateTo: Custom date range (自定义日期范围, ISO 8601)

  • priority: [0=none (无), 1=low (低), 3=medium (中), 5=high (高)]

SORTING:

  • sortBy: "dueDate" (截止日期, default), "priority" (优先级), "createdTime" (创建时间)

  • sortOrder: "asc" (升序, default), "desc" (降序)

⚠️ LIMITATION: Only returns UNCOMPLETED tasks (未完成任务, status=0). Completed tasks not available.

EXAMPLES:

  • Today's tasks (今天的任务): { "preset": "today" }

  • High priority from inbox (收集箱高优先级): { "projectId": "inbox", "priority": [5] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of tasks to return (最大返回数量, default 50, max 200)
presetNoQuick date filter preset (快速筛选): today (今天), tomorrow (明天), thisWeek (本周), overdue (逾期)
sortByNoSort field (排序字段): dueDate (截止日期, default), priority (优先级), createdTime (创建时间)
priorityNoFilter by priority (优先级): 0=none (无), 1=low (低), 3=medium (中), 5=high (高)
dueDateToNoFilter tasks with due date <= this value (截止日期结束, ISO 8601 format)
projectIdNoProject ID(s) (清单ID) to filter. Use "inbox" for inbox tasks (收集箱). If omitted, searches all projects (所有清单).
sortOrderNoSort order (排序方向): asc (升序, default), desc (降序)
dueDateFromNoFilter tasks with due date >= this value (截止日期起始, ISO 8601 format)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tasksYes
totalYes
filteredYes
projectsYes
Behavior5/5

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

The description discloses the key limitation that only uncompleted tasks are returned, and explains sorting and filtering behavior. No annotations exist, so the description fully covers behavioral aspects.

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 clear sections and bullet points, making it easy to scan. However, it is somewhat lengthy and contains some redundancy with the schema, which could be trimmed.

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?

The description is comprehensive: it covers usage, exclusions, quick filters, optional filters, sorting, a limitation, and examples. Given the tool's complexity (8 optional params, no required), this is complete.

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?

Schema description coverage is 100%, so parameters are already documented. The description adds value by including Chinese translations, examples, and clarifying use cases for presets, but some repetition exists.

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?

The description clearly states the tool lists and filters tasks across projects. It uses specific verbs ('List and filter tasks') and distinguishes from sibling tools like get_project_data and get_task.

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' and 'WHEN NOT TO USE' sections with direct references to alternatives (get_project_data, get_task). This provides clear guidance on tool selection.

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/evalor/Dida365MCP'

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