Skip to main content
Glama

get-projects

Retrieve all Todoist projects to view, organize, or manage your task lists and workflows.

Instructions

Get all the projects from Todoist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'todoist_get_projects' which fetches projects using TodoistClient and returns them as JSON string.
    case 'todoist_get_projects':
      const projects = await this.todoistClient.getProjects()
      return this.createResponse(requestId, {
        content: [
          {
            type: 'text',
            text: JSON.stringify(projects, null, 2)
          }
        ]
      })
  • Tool schema definition for todoist_get_projects, including empty input schema.
      name: 'todoist_get_projects',
      description: 'Get projects from Todoist',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • Tool visibility registration enabling todoist_get_projects.
    todoist_get_projects: true,
  • TodoistClient helper method that makes API call to fetch projects.
    async getProjects(): Promise<TodoistProject[]> {
      return this.makeRequest<TodoistProject[]>('GET', '/projects');
    }
  • TypeScript interface defining the TodoistProject type returned by getProjects.
    export interface TodoistProject {
      id: string;
      name: string;
      comment_count: number;
      order: number;
      color: string;
      is_shared: boolean;
      is_favorite: boolean;
      is_inbox_project: boolean;
      is_team_inbox: boolean;
      view_style: string;
      url: string;
      parent_id: string | null;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without behavioral details. It doesn't disclose whether this is a read-only operation, if it requires authentication, how results are returned (e.g., pagination, format), or any rate limits—critical gaps for a tool that fetches data.

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?

The description is a single, efficient sentence that front-loads the core purpose with zero waste. Every word ('Get all the projects from Todoist') directly contributes to understanding the tool's function, making it optimally concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is incomplete for a data-fetching tool. It lacks details on return values (e.g., project fields, format), authentication needs, or error handling, leaving significant gaps despite the simple parameterless design.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't mention parameters, earning a baseline 4 for not adding unnecessary information beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get') and resource ('projects from Todoist'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get-project-id' or 'get-tasks', which would require more specificity about scope or output format to earn a 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'get-project-id' (for a single project) or 'get-tasks' (for tasks instead of projects). It lacks explicit when/when-not instructions or named alternatives, leaving usage context implied at best.

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/kentaroh7777/mcp-todoist'

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