Skip to main content
Glama
mikemc

Todoist MCP Server

by mikemc

todoist_get_project

Retrieve a specific project from Todoist using its unique project ID. Enables users to access and manage project details directly through the Todoist MCP Server.

Instructions

Get a single project from Todoist

Args: project_id: ID of the project to retrieve

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes

Implementation Reference

  • The core handler function for the 'todoist_get_project' tool. It retrieves a specific Todoist project by its ID using the shared Todoist API client from the request context, handles errors, and returns the project data as JSON.
    def todoist_get_project(ctx: Context, project_id: str) -> str:
        """Get a single project from Todoist
    
        Args:
            project_id: ID of the project to retrieve
        """
        todoist_client = ctx.request_context.lifespan_context.todoist_client
    
        try:
            logger.info(f"Getting project with ID: {project_id}")
    
            project = todoist_client.get_project(project_id=project_id)
    
            if not project:
                logger.info(f"No project found with ID: {project_id}")
                return f"No project found with ID: {project_id}"
    
            logger.info(f"Retrieved project: {project.id}")
            return json.dumps(project.to_dict(), indent=2, default=str)
        except Exception as error:
            logger.error(f"Error getting project: {error}")
            return f"Error getting project: {str(error)}"
  • src/main.py:73-73 (registration)
    Registration of the 'todoist_get_project' tool using the FastMCP decorator, which automatically generates schema from the function signature and registers it with the MCP server.
    mcp.tool()(todoist_get_project)
  • src/main.py:12-18 (registration)
    Import of the 'todoist_get_project' handler function from the projects module into main.py for registration.
    from .projects import (
        todoist_get_projects,
        todoist_get_project,
        todoist_add_project,
        todoist_update_project,
        todoist_delete_project,
    )
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 it 'retrieves' a project. It doesn't disclose whether this requires authentication, has rate limits, returns error conditions, or what format the response takes. For a read operation with zero annotation coverage, this leaves significant behavioral gaps.

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

Conciseness3/5

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

The description is appropriately brief with a clear purpose statement followed by parameter documentation. However, the 'Args:' section formatting is somewhat redundant when there's only one parameter, and the overall content could be more front-loaded with critical information.

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?

For a tool with no annotations, no output schema, and minimal parameter documentation, the description is incomplete. It doesn't explain what information is returned about the project, error handling, authentication requirements, or how this differs from the plural 'get_projects' 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?

With 0% schema description coverage and only 1 parameter, the description adds crucial meaning by explaining that 'project_id' is the 'ID of the project to retrieve'. This fully compensates for the schema gap, though it doesn't provide format examples or constraints.

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 verb 'Get' and resource 'a single project from Todoist', which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling 'todoist_get_projects' (plural) beyond the 'single project' phrasing, which is implied but not explicit.

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 'todoist_get_projects' or 'todoist_get_task'. It mentions retrieving by project_id but doesn't explain when you'd want a single project versus listing all projects or working with tasks/sections.

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

Related 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/mikemc/todoist-mcp-server'

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