Skip to main content
Glama
Doist
by Doist

find-project-collaborators

Read-onlyIdempotent

Search for Todoist collaborators by name or email to find their user ID. Supports partial matches and can limit search to a specific project.

Instructions

Find Todoist users (collaborators, teammates) by name or email to look up their user ID. Use this whenever the user asks to find, look up, or identify a person — e.g. "find Carrie's user ID", "who is Ernesto", "look up a user". When projectId is omitted, searches across the collaborators of every shared project the authenticated user has access to, plus the authenticated user themselves — an empty result means the person is not a collaborator on any project you share with them, not necessarily that they do not exist in Todoist. When projectId is provided, searches only that project. Partial, case-insensitive match on name and email.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdNoOptional. If provided, searches only collaborators of this project. If omitted, searches across the collaborators of all shared projects the authenticated user can access (plus the authenticated user themselves) — use this for general "find a user" / "who is X" lookups.
searchTermNoSearch for a user by name or email (partial and case insensitive match). If omitted, all users are returned.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalCountYesThe total number of users found.
projectInfoNoInformation about the project (only present when projectId was provided).
collaboratorsYesThe found users.
appliedFiltersYesThe filters that were applied to the search.
totalAvailableNoThe total number of available users before the search filter was applied.
Behavior5/5

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

Description adds context beyond annotations: explains scope of search (all shared projects + self), partial/case-insensitive matching, and interprets empty results. Annotations already declare readOnlyHint and idempotentHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with main purpose upfront followed by details and caveats. Slightly long but every sentence adds value.

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 simplicity of the tool (2 optional params), the description covers search behavior, project scoping, and matching semantics. Output schema exists, so return values are documented elsewhere.

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%. Description adds extra meaning: explains behavior when projectId omitted and that omitting searchTerm returns all users. This adds value beyond 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 the tool finds Todoist users by name/email to look up user IDs. It uses specific verbs and distinguishes from sibling tools like find-tasks or user-info.

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 says when to use (e.g., 'find Carrie's user ID') and when to omit projectId for general search. Also provides caveats about empty results and partial matching.

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