Skip to main content
Glama
Doist
by Doist

find-labels

Read-onlyIdempotent

Retrieve Todoist labels with optional name search and pagination. Returns personal labels with full metadata and shared labels as names.

Instructions

List personal labels and shared labels. Personal labels have full metadata (id, name, color, order, isFavorite) and support pagination and name search (partial, case insensitive). Shared labels are labels used on tasks shared with you — they are returned as names only (no IDs or metadata). When searching, all matching personal labels are fetched across all pages and returned as a single result set (limit and cursor are ignored). When not searching, personal labels are returned with pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoThe maximum number of labels to return.
cursorNoThe cursor to get the next page of labels (cursor is obtained from the previous call to this tool, with the same parameters). Ignored when searchText is provided.
searchTextNoSearch for a label by name (partial and case insensitive match). Supports wildcards (e.g. "work*" for prefix match). Use "\*" for a literal asterisk. If omitted, all labels are returned.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelsYesThe found personal labels.
hasMoreYesWhether there are more results available.
nextCursorNoCursor for the next page of results.
totalCountYesThe total number of labels in this page.
sharedLabelsYesNames of all shared labels visible to you. These have no IDs or metadata — use their names directly when filtering tasks.
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 safe read operation. Description adds crucial details: pagination behavior, search ignoring limit/cursor, shared labels lacking IDs. No contradictions with annotations.

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 front-loaded purpose. Each sentence provides useful information, though slightly verbose. Could be tightened without losing clarity.

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?

Comprehensive coverage of label types, metadata, pagination, and search behavior. With an output schema present, return values are not needed. No gaps for a list 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 descriptions cover 100% of parameters. Description adds value by explaining when limit/cursor are used and that searchText supports wildcards and overrides pagination.

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 'List personal labels and shared labels' with specific details about metadata differences. Distinguishes itself from sibling tools like find-tasks by focusing on labels.

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?

Provides context for when to use (listing labels) and explains behavior differences between search and non-search. Does not explicitly mention when not to use or alternatives, but context is clear.

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