list_todos
List to-dos from a specific Things 3 list, area, or project; filter by status, tags, or limit for a focused view of your tasks.
Instructions
List Things 3 to-dos within one scope.
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": {
"scope_type": "<scope_type>",
"scope_name": "<scope_name>"
},
"name": "list_todos"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | Only return to-dos carrying ANY of these tags (comma-separated, case-insensitive). Empty = no tag filter. Filter here rather than client-side: the tag, not the area, is what identifies e.g. a purchase decision, and a to-do filed in no area is the normal case. | |
| limit | No | Return at most N to-dos (0 = all). Applied AFTER the tag filter. | |
| status | No | Filter — "open" (default), "completed", "canceled" or "any". | open |
| scope_name | Yes | Name of the list/area/project. Built-in lists include "Inbox", "Today", "Anytime", "Upcoming", "Someday", "Logbook". | |
| scope_type | Yes | One of "list", "area", "project". | |
| include_notes | No | False drops the `notes` field. Notes dominate the payload (72 % of a real 95-to-do list) — leave them out for overviews and fetch them per to-do with get_todo() when you actually need them. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |