Skip to main content
Glama
Sign In
Todoist MCP Server

Todoist MCP Server

by greirson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

todoist_shared_labels_get

Fetch all shared labels from your Todoist workspace, enabling team collaboration on tasks with Business accounts.

Instructions

Get all shared labels in the workspace. Shared labels are available in Todoist Business accounts for team collaboration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "todoist_shared_labels_get"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.3

TDQS

A3.8/5.0
Behavior2/5

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

No annotations exist, but description only states it's a read operation ('Get'). It does not disclose auth requirements, rate limits, pagination, or error conditions. Given no annotations, the description carries the burden and is insufficient.

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 main purpose, second adds context. No redundant information, appropriately sized, 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?

For a simple retrieval tool with no parameters or output schema, the description explains purpose and account requirement. Could mention prerequisites or permissions, but adequate for most agents.

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?

Zero parameters with 100% schema coverage. Baseline is 3, but description adds value by clarifying what 'shared labels' means (team collaboration in Business accounts), which is not in 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?

Description clearly states 'Get all shared labels in the workspace', specifying verb, resource, and scope. It also explains what shared labels are, distinguishing this tool from siblings like 'todoist_label_get' which retrieves a single label.

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

Usage Guidelines3/5

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

Description mentions 'available in Todoist Business accounts for team collaboration', implying usage context. However, no explicit when-to-use alternatives like 'todoist_label_get' or conditions like not without a Business account. Minimal guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools