Skip to main content
Glama
vitalio-sh

Enhanced Todoist MCP Server Extended

todoist_update_section

Modify an existing section's name in Todoist to reorganize tasks and projects for better workflow management.

Instructions

Update an existing section

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionIdYesThe ID of the section to update
nameYesNew name for the section

Implementation Reference

  • The handler logic that executes the todoist_update_section tool by calling todoistClient.updateSection with the provided sectionId and new name.
    if (name === "todoist_update_section") {
      if (!isUpdateSectionArgs(args)) {
        throw new Error("Invalid arguments for todoist_update_section");
      }
    
      const updatedSection = await todoistClient.updateSection(args.sectionId, { name: args.name });
      
      return {
        content: [{ 
          type: "text", 
          text: `Section updated successfully:\nID: ${updatedSection.id}\nName: ${updatedSection.name}` 
        }],
        isError: false,
      };
    }
  • The Tool schema definition for todoist_update_section, including name, description, and inputSchema requiring sectionId and name.
    const UPDATE_SECTION_TOOL: Tool = {
      name: "todoist_update_section",
      description: "Update an existing section",
      inputSchema: {
        type: "object",
        properties: {
          sectionId: {
            type: "string",
            description: "The ID of the section to update"
          },
          name: {
            type: "string",
            description: "New name for the section"
          }
        },
        required: ["sectionId", "name"]
      }
    };
  • src/index.ts:1103-1107 (registration)
    Registration of the UPDATE_SECTION_TOOL in the array of tools returned by the ListToolsRequestSchema handler.
    // Section tools
    GET_SECTIONS_TOOL,
    CREATE_SECTION_TOOL,
    UPDATE_SECTION_TOOL,
    DELETE_SECTION_TOOL,
  • Type guard helper function isUpdateSectionArgs used to validate input arguments for the todoist_update_section tool.
    function isUpdateSectionArgs(args: unknown): args is {
      sectionId: string;
      name: string;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "sectionId" in args &&
        "name" in args &&
        typeof (args as { sectionId: string; name: string }).sectionId === "string" &&
        typeof (args as { sectionId: string; name: string }).name === "string"
      );
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'update' implies a mutation, the description doesn't specify whether this requires specific permissions, what happens to the existing section data, if changes are reversible, or any rate limits/error conditions. This leaves significant gaps for a mutation tool.

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 front-loaded with the core action ('update an existing section'), making it immediately clear without unnecessary elaboration.

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 the tool returns, error handling, or behavioral nuances like idempotency. Given the complexity of an update operation, more context is needed to guide the agent effectively.

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?

The schema description coverage is 100%, with both parameters ('sectionId' and 'name') clearly documented in the schema. The description adds no additional parameter semantics beyond what's in the schema, so it meets the baseline for high schema coverage without compensating value.

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 ('update') and resource ('existing section'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'todoist_update_project' or 'todoist_update_task' beyond specifying 'section' as the target resource, which is why it doesn't reach a perfect score.

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. It doesn't mention prerequisites (e.g., needing an existing section ID), exclusions, or compare it to related tools like 'todoist_create_section' or 'todoist_delete_section', leaving the agent to infer usage from context 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