Skip to main content
Glama
Doist
by Doist

find-completed-tasks

Read-onlyIdempotent

Retrieve completed tasks within a specified date range, filtering by project, labels, or assignee to answer "what got done?" queries.

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
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.
hasMoreYes
nextCursorNo
totalCountYesThe total number of tasks in this page.
appliedFiltersYes
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive. The description does not contradict these and adds practical usage context (e.g., setting responsibleUser to current user). It lacks an explicit statement about no side effects, but annotations cover that, so slight extra info is beneficial.

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?

Description is succinct and well-structured, with no redundant or fluff content. Each sentence adds value, covering usage distinctions and defaults clearly.

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 the tool's many filtering options, the description provides essential context for understanding its primary use case and key differentiators. It does not enumerate every filter, but those are fully defined in the schema, making the overall context 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 covers all 12 parameters with detailed descriptions, including patterns, defaults, and enums. The tool description adds extra guidance on responsibleUser usage and reinforces defaults, which supplements rather than repeats, giving a 4 over the baseline 3.

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?

Clearly states the tool's function: 'Get completed tasks in a date range' and distinguishes it from find-activity which reports completion events, including recurring instances. This precise scoping makes the purpose unmistakable.

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 directs users to use find-activity for 'what did I complete/get done' queries, and explains default date windows and responsibleUser behavior. This gives strong guidance on when to choose this tool over alternatives.

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-mcp'

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