Skip to main content
Glama
vitalio-sh

Enhanced Todoist MCP Server Extended

todoist_create_project

Create a new Todoist project with customizable name, color, view style, and optional sub-project structure to organize tasks effectively.

Instructions

Create a new project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the project
parentIdNoParent project ID for creating a sub-project (optional)
colorNoProject color (optional)
isFavoriteNoWhether to mark as favorite (optional)
viewStyleNoProject view style: 'list' or 'board' (optional)

Implementation Reference

  • Handler implementation for the todoist_create_project tool. Validates input using isCreateProjectArgs, constructs project data, calls todoistClient.addProject(), and returns formatted success response with project details.
    if (name === "todoist_create_project") {
      if (!isCreateProjectArgs(args)) {
        throw new Error("Invalid arguments for todoist_create_project");
      }
      
      const projectData: any = { name: args.name };
      if (args.parentId) projectData.parentId = args.parentId;
      if (args.color) projectData.color = args.color;
      if (args.isFavorite !== undefined) projectData.isFavorite = args.isFavorite;
      if (args.viewStyle) projectData.viewStyle = args.viewStyle;
    
      const project = await todoistClient.addProject(projectData);
      return {
        content: [{ 
          type: "text", 
          text: `Project created successfully:\nID: ${project.id}\n${formatProject(project)}` 
        }],
        isError: false,
      };
    }
  • Tool schema definition for todoist_create_project, including input schema with properties like name (required), parentId, color, isFavorite, viewStyle.
    const CREATE_PROJECT_TOOL: Tool = {
      name: "todoist_create_project",
      description: "Create a new project",
      inputSchema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "The name of the project"
          },
          parentId: {
            type: "string",
            description: "Parent project ID for creating a sub-project (optional)"
          },
          color: {
            type: "string",
            description: "Project color (optional)"
          },
          isFavorite: {
            type: "boolean",
            description: "Whether to mark as favorite (optional)"
          },
          viewStyle: {
            type: "string",
            description: "Project view style: 'list' or 'board' (optional)",
            enum: ["list", "board"]
          }
        },
        required: ["name"]
      }
    };
  • src/index.ts:1098-1102 (registration)
    Registration of todoist_create_project tool (as CREATE_PROJECT_TOOL) in the tools array returned by ListToolsRequestSchema handler.
    GET_PROJECTS_TOOL,
    GET_PROJECT_TOOL,
    CREATE_PROJECT_TOOL,
    UPDATE_PROJECT_TOOL,
    DELETE_PROJECT_TOOL,
  • Type guard helper function isCreateProjectArgs used to validate arguments in the tool handler.
    function isCreateProjectArgs(args: unknown): args is {
      name: string;
      parentId?: string;
      color?: string;
      isFavorite?: boolean;
      viewStyle?: string;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "name" in args &&
        typeof (args as { name: string }).name === "string"
      );
    }
  • Helper function formatProject used to format project details in tool responses.
    function formatProject(project: any): string {
      return `- ${project.name}${project.color ? `\n  Color: ${project.color}` : ''}${project.isFavorite ? `\n  Favorite: Yes` : ''}${project.viewStyle ? `\n  View: ${project.viewStyle}` : ''}${project.parentId ? `\n  Parent: ${project.parentId}` : ''}${project.id ? ` (ID: ${project.id})` : ''}`;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Create a new project' implies a write/mutation operation but doesn't specify permissions needed, whether it's idempotent, what happens on duplicate names, or what the response contains. For a mutation tool with zero annotation coverage, this 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?

The description is a single, efficient sentence that states the core purpose without any wasted words. It's appropriately sized for a simple creation operation and gets straight to the point.

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 mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after creation, what permissions are required, or how to handle errors. Given the complexity of creating a project with multiple optional parameters, more context about the operation's behavior is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all parameters are documented in the schema. The description adds no additional parameter information beyond what's already in the structured schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 'Create a new project' clearly states the verb ('Create') and resource ('project'), making the purpose immediately understandable. However, it doesn't differentiate this from sibling tools like 'todoist_create_task' or 'todoist_create_label', which follow the same pattern for different resources.

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. With siblings like 'todoist_update_project' and 'todoist_get_projects', there's no indication of when creation is appropriate versus retrieval or modification. No prerequisites or exclusions are mentioned.

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/vitalio-sh/todoist-mcp-server-ext'

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