Skip to main content
Glama
Doist
by Doist

find-projects

Read-onlyIdempotent

Search and list Todoist projects by name, with filters for active, archived, or all projects. Supports partial matches and pagination.

Instructions

List all projects or search for projects by name. By default only active projects are returned; use archivedStatus ('archived' or 'all') to include archived projects. When searching or when archivedStatus is 'all', all matching projects are returned (pagination is ignored). Otherwise projects are returned with pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoThe maximum number of projects to return.
cursorNoThe cursor to get the next page of projects (cursor is obtained from the previous call to this tool, with the same parameters).
searchTextNoSearch for a project by name (partial and case insensitive match). Supports wildcards (e.g. "work*" for prefix match). Use "\*" for a literal asterisk. If omitted, all projects are returned.
archivedStatusNoWhich projects to return by archive status: 'active' (default, non-archived only), 'archived' (archived only), or 'all' (both active and archived). Each project includes an isArchived field. Archived projects can be deleted via the delete-object tool (type: 'project').

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hasMoreYesWhether there are more results available.
projectsYesThe found projects.
nextCursorNoCursor for the next page of results.
totalCountYesThe total number of projects in this page.
appliedFiltersYesThe filters that were applied to the search.
Behavior5/5

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

Annotations already indicate read-only and non-destructive behavior. The description adds critical details: pagination is ignored when searching or using archivedStatus='all', each project has an isArchived field, and archived projects can be deleted via delete-object. No contradictions.

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 concise sentences: purpose, default behavior, and pagination rules. No wasted words, front-loaded with key information.

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?

Given the presence of an output schema, the description covers all necessary behavioral aspects: pagination, search syntax, archiving. It also hints at related tools (delete-object). Complete for a read-only listing tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds value by explaining searchText wildcards, case insensitivity, and the relationship between archivedStatus and isArchived field. It also clarifies pagination behavior beyond the schema.

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 or searches projects, distinguishing it from sibling tools like find-tasks or find-comments. It specifies default behavior (only active) and the archivedStatus option.

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 searchText, archivedStatus, and how pagination interacts with these parameters. It provides clear context but does not explicitly exclude use cases or mention 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-ai'

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