Todoist MCP Server

find-completed-tasks

Read-onlyIdempotent

Retrieve tasks completed within a date range, with optional filters for project, labels, section, or assignee. Answers 'what did I complete' by completion or due date.

Instructions

Get completed tasks in a date range. For "what did I complete/get done" questions, use find-activity instead — it reports completion events, including every occurrence of a recurring task, which this tool does not. since/until are optional and default to a 7-day window when omitted. Includes all collaborators by default. Person-specific queries (summaries, plans, reports) require responsibleUser.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`getBy`	No	The method to use to get the tasks: "completion" to get tasks by completion date (ie, when the task was actually completed), "due" to get tasks by due date (ie, when the task was due to be completed by).	completion
`limit`	No	The maximum number of tasks to return.
`since`	No	Optional start date for completed tasks. Format: YYYY-MM-DD. Defaults to 6 days before until (or today if until is omitted), resulting in a 7-day window.
`until`	No	Optional end date for completed tasks. Format: YYYY-MM-DD. Defaults to 6 days after since (or today if since is omitted), resulting in a 7-day window.
`cursor`	No	The cursor to get the next page of tasks (cursor is obtained from the previous call to this tool, with the same parameters).
`labels`	No	The labels to filter the tasks by
`parentId`	No	The ID of the parent task to get the tasks for.
`projectId`	No	The ID of the project to get the tasks for. Project ID should be an ID string, or the text "inbox", for inbox tasks.
`sectionId`	No	The ID of the section to get the tasks for.
`workspaceId`	No	The ID of the workspace to get the tasks for.
`labelsOperator`	No	The operator to use when filtering by labels. This will dictate whether a task has all labels, or some of them. Default is "or".
`responsibleUser`	No	Filter completed tasks assigned to this user. User ID, name, or email. For personal queries (summaries, plans, reports), set to current user from user-info to exclude collaborators. Defaults to all collaborators.

Output Schema

TableJSON Schema

Name	Required	Description
`tasks`	Yes	The found completed tasks.
`hasMore`	Yes
`nextCursor`	No
`totalCount`	Yes	The total number of tasks in this page.
`appliedFilters`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv13.3.1Sep 22, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds valuable behavioral context beyond that: the 7-day default window, all-collaborator scope by default, and the exclusion of recurring-task occurrences. This addresses likely agent misconceptions about the tool's results.

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?

Three sentences deliver the essential scoping, the alternative tool, and key defaults without redundancy. The most important information (what the tool does) is front-loaded, and every sentence earns its place. No filler or repetition.

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

Completeness4/5

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

For a 12-parameter tool with a rich schema and output schema, the description covers the key decision points: purpose, alternative, date-range defaults, collaborator handling, and responsibleUser requirement. It does not explain pagination or filter specifics, but those are fully documented in the schema and annotations, so the description is sufficiently complete for correct invocation.

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 description coverage is 100%, so the baseline is 3. The description repeats default-window information already in the schema and mentions responsibleUser for person-specific queries, which adds a small usage hint. However, it does not meaningfully compensate beyond what the schema provides, so 3 is appropriate.

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 opens with 'Get completed tasks in a date range,' naming the verb, resource, and scope. It further distinguishes from find-activity by noting that find-activity reports completion events including every recurring task occurrence, which this tool does not. This makes the tool's unique role clear relative to siblings.

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?

Explicitly instructs when to use find-activity instead ('For "what did I complete/get done" questions'), and clarifies that this tool excludes recurring-task occurrences. It also states date-range defaults and collaborator behavior, plus the requirement for responsibleUser in person-specific queries, leaving little ambiguity about selection.

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