Skip to main content
Glama
vitalio-sh

Enhanced Todoist MCP Server Extended

todoist_update_project

Modify an existing Todoist project by updating its name, color, favorite status, or view style to reflect changes in your workflow organization.

Instructions

Update an existing project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesThe ID of the project to update
nameNoNew name for the project (optional)
colorNoNew color for the project (optional)
isFavoriteNoWhether to mark as favorite (optional)
viewStyleNoProject view style: 'list' or 'board' (optional)

Implementation Reference

  • Handler function for the 'todoist_update_project' tool. Validates arguments using isUpdateProjectArgs, constructs update data from provided fields (name, color, isFavorite, viewStyle), calls todoistClient.updateProject, and returns formatted success response with updated project details.
    if (name === "todoist_update_project") {
      if (!isUpdateProjectArgs(args)) {
        throw new Error("Invalid arguments for todoist_update_project");
      }
    
      const updateData: any = {};
      if (args.name) updateData.name = args.name;
      if (args.color) updateData.color = args.color;
      if (args.isFavorite !== undefined) updateData.isFavorite = args.isFavorite;
      if (args.viewStyle) updateData.viewStyle = args.viewStyle;
    
      const updatedProject = await todoistClient.updateProject(args.projectId, updateData);
      
      return {
        content: [{ 
          type: "text", 
          text: `Project updated successfully:\nID: ${updatedProject.id}\n${formatProject(updatedProject)}` 
        }],
        isError: false,
      };
    }
  • Tool schema definition for 'todoist_update_project', specifying input parameters including required projectId and optional fields for update.
    const UPDATE_PROJECT_TOOL: Tool = {
      name: "todoist_update_project",
      description: "Update an existing project",
      inputSchema: {
        type: "object",
        properties: {
          projectId: {
            type: "string",
            description: "The ID of the project to update"
          },
          name: {
            type: "string",
            description: "New name for the project (optional)"
          },
          color: {
            type: "string",
            description: "New color for the project (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: ["projectId"]
      }
    };
  • src/index.ts:1083-1121 (registration)
    Registration of the UPDATE_PROJECT_TOOL in the list of available tools returned by ListToolsRequestSchema handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        // Task tools
        CREATE_TASK_TOOL,
        QUICK_ADD_TASK_TOOL,
        GET_TASKS_TOOL,
        GET_TASK_TOOL,
        UPDATE_TASK_TOOL,
        DELETE_TASK_TOOL,
        COMPLETE_TASK_TOOL,
        REOPEN_TASK_TOOL,
        SEARCH_TASKS_TOOL,
        MOVE_TASK_TOOL,
        BULK_MOVE_TASKS_TOOL,
        // Project tools
        GET_PROJECTS_TOOL,
        GET_PROJECT_TOOL,
        CREATE_PROJECT_TOOL,
        UPDATE_PROJECT_TOOL,
        DELETE_PROJECT_TOOL,
        // Section tools
        GET_SECTIONS_TOOL,
        CREATE_SECTION_TOOL,
        UPDATE_SECTION_TOOL,
        DELETE_SECTION_TOOL,
        // Label tools
        CREATE_LABEL_TOOL,
        GET_LABEL_TOOL,
        GET_LABELS_TOOL,
        UPDATE_LABEL_TOOL,
        DELETE_LABEL_TOOL,
        // Comment tools
        CREATE_COMMENT_TOOL,
        GET_COMMENT_TOOL,
        GET_COMMENTS_TOOL,
        UPDATE_COMMENT_TOOL,
        DELETE_COMMENT_TOOL,
      ],
    }));
  • Type guard helper function to validate input arguments for the todoist_update_project tool, ensuring projectId is present as string.
    function isUpdateProjectArgs(args: unknown): args is {
      projectId: string;
      name?: string;
      color?: string;
      isFavorite?: boolean;
      viewStyle?: string;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "projectId" in args &&
        typeof (args as { projectId: string }).projectId === "string"
      );
    }
  • Helper function to format project details for output in tool responses, used by todoist_update_project handler.
    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?

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'update' implying mutation, but doesn't mention permissions needed, whether changes are reversible, rate limits, or what happens to unspecified fields. This is inadequate for a mutation tool with zero annotation coverage.

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 with zero wasted words. It's appropriately sized and front-loaded with the essential action, making it easy to parse quickly.

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 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what happens on success/failure, return values, or behavioral constraints. The agent lacks crucial context for safe and effective use.

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 parameters are well-documented in the schema. The description adds no additional meaning beyond the schema's parameter documentation. Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Update an existing project' clearly states the verb ('update') and resource ('project'), but it's vague about what aspects can be updated and doesn't distinguish from sibling tools like todoist_update_task or todoist_update_label. It provides basic purpose but lacks specificity.

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?

No guidance is provided on when to use this tool versus alternatives like todoist_create_project or other update tools. The description doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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