Skip to main content
Glama
Doist
by Doist

find-completed-tasks

Read-onlyIdempotent

Retrieve completed tasks from Todoist filtered by date, project, labels, or assignee. Supports pagination and specific user queries.

Instructions

Get completed tasks. 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
NameRequiredDescriptionDefault
getByNoThe 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
limitNoThe maximum number of tasks to return.
sinceNoOptional 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.
untilNoOptional 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.
cursorNoThe cursor to get the next page of tasks (cursor is obtained from the previous call to this tool, with the same parameters).
labelsNoThe labels to filter the tasks by
parentIdNoThe ID of the parent task to get the tasks for.
projectIdNoThe ID of the project to get the tasks for. Project ID should be an ID string, or the text "inbox", for inbox tasks.
sectionIdNoThe ID of the section to get the tasks for.
workspaceIdNoThe ID of the workspace to get the tasks for.
labelsOperatorNoThe operator to use when filtering by labels. This will dictate whether a task has all labels, or some of them. Default is "or".
responsibleUserNoFilter 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
NameRequiredDescriptionDefault
tasksYesThe found completed tasks.
hasMoreYesWhether there are more results available.
nextCursorNoCursor for the next page of results.
totalCountYesThe total number of tasks in this page.
appliedFiltersYesThe filters that were applied to the search.
Behavior4/5

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

Annotations already indicate a safe read operation. The description adds behavioral details: defaults for since/until, inclusion of all collaborators, and the condition for person-specific queries. This goes beyond annotations to explain default behavior.

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 sentences: first states the purpose, second provides critical defaults and conditions. No redundant or irrelevant information. Perfectly concise and front-loaded.

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?

Given 12 parameters, 0 required, and an output schema, the description covers the most important behavioral aspects (date defaults, collaborator inclusion, user-specific queries). It could mention pagination (cursor), but the output schema likely covers that. Overall adequate for a read-only tool.

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 coverage is 100%, so the schema already documents all parameters. The description adds value by explaining the default date window and the context for responsibleUser, which is not fully captured in the schema descriptions.

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 'Get completed tasks' which is specific and distinct from sibling tools like find-tasks (non-completed) and find-tasks-by-date (all tasks). It adds context about date windows and collaborator inclusion, further clarifying its scope.

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

Usage Guidelines4/5

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

The description explains when to use it (completed tasks), defaults (7-day window, all collaborators), and special conditions (person-specific queries require responsibleUser). It does not explicitly exclude alternatives, but the purpose is clear enough to differentiate.

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/Doist/todoist-ai'

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