Skip to main content
Glama

get_project

Retrieve a specific Todoist project by its ID to view project details and manage associated tasks.

Instructions

Get a specific project by ID.

Args:
    project_id: The ID of the project to retrieve

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler for 'get_project'. It checks the client, fetches the project using the TodoistClient, and formats the response as a string.
    @mcp.tool()
    async def get_project(project_id: str) -> str:
        """Get a specific project by ID.
        
        Args:
            project_id: The ID of the project to retrieve
        """
        _check_client()
        
        project = await todoist_client.get_project(project_id)
        
        return (
            f"Project: {project.name}\n"
            f"ID: {project.id}\n"
            f"Color: {project.color}\n"
            f"Shared: {project.is_shared}\n"
            f"Favorite: {project.is_favorite}\n"
            f"View Style: {project.view_style}\n"
            f"URL: {project.url}"
        )
  • The TodoistClient helper method that performs the actual API call to retrieve project details and parses it into TodoistProject model.
    async def get_project(self, project_id: str) -> TodoistProject:
        """Get a specific project by ID."""
        data = await self._request("GET", f"/projects/{project_id}")
        return TodoistProject(**data)
  • Pydantic model defining the structure of a TodoistProject used in the tool response.
    class TodoistProject(BaseModel):
        """Represents a Todoist project."""
        id: str
        name: str
        comment_count: int = 0
        order: int = 0
        color: str = "grey"
        is_shared: bool = False
        is_favorite: bool = False
        is_inbox_project: bool = False
        is_team_inbox: bool = False
        view_style: str = "list"
        url: str = ""
        parent_id: Optional[str] = None
  • The @mcp.tool() decorator registers the get_project function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a retrieval operation but doesn't describe authentication requirements, rate limits, error behavior (e.g., what happens with invalid ID), or response format. The presence of an output schema helps but the description itself lacks behavioral context.

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 perfectly concise with zero wasted words. It states the purpose in one clear sentence and documents the parameter in a clean, structured format. Every element earns its place and the information is front-loaded appropriately.

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 read operation with one parameter and an output schema, the description provides adequate context. The output schema will handle return value documentation, so the description focuses correctly on purpose and parameter semantics. However, it could better address behavioral aspects given the lack of annotations.

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 description explicitly documents the single parameter ('project_id: The ID of the project to retrieve'), adding clear semantic meaning beyond the schema's minimal title ('Project Id'). With 0% schema description coverage, this parameter documentation is essential and well-handled for a single-parameter tool.

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 specific project by ID'), making the purpose unambiguous. It distinguishes from sibling 'get_projects' by specifying retrieval of a single project rather than a list. However, it doesn't fully differentiate from 'get_task' which retrieves a different resource type.

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?

The description implies usage when you need to retrieve a single project by its ID, but doesn't explicitly state when to use this versus 'get_projects' (for listing) or other siblings. No guidance is provided about prerequisites, error conditions, or alternative tools for related operations.

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

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