Skip to main content
Glama

create_sections

Organize Todoist projects by adding structured sections to categorize and group related tasks effectively.

Instructions

Create new sections in Todoist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes

Implementation Reference

  • Core execution logic for the 'create_sections' tool (create mode): POSTs each item to Todoist API at '/sections' with parameters name, project_id, and optional order, returning the created item.
    // Create mode
    else {
        finalPath = options.path || options.basePath || '';
    
        let result;
        switch (options.method) {
            case 'GET':
                result = await todoistApi.get(finalPath, apiParams);
                break;
            case 'POST':
                result = await todoistApi.post(finalPath, apiParams);
                break;
            case 'DELETE':
                result = await todoistApi.delete(finalPath);
                break;
        }
    
        return {
            success: true,
            created_item: result,
        };
    }
  • Registers the 'create_sections' MCP tool using createBatchApiHandler, specifying the schema, HTTP method, path, and create mode for batch section creation in Todoist.
    createBatchApiHandler({
        name: 'create_sections',
        description: 'Create new sections in Todoist',
        itemSchema: {
            name: z.string(),
            project_id: z.string(),
            order: z.number().int().optional(),
        },
        method: 'POST',
        path: '/sections',
        mode: 'create',
    });
  • Zod schema definition for individual section creation input: requires name and project_id, optional order.
    itemSchema: {
        name: z.string(),
        project_id: z.string(),
        order: z.number().int().optional(),
    },
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 creation operation, implying mutation, but doesn't address permissions, rate limits, error conditions, or what happens on success (e.g., whether it returns IDs). 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 with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place without being overly terse.

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?

Given this is a mutation tool with no annotations, 0% schema description coverage, and no output schema, the description is incomplete. It doesn't explain what sections are, how they relate to projects/tasks, what the tool returns, or any behavioral constraints, making it inadequate for safe and effective use by an agent.

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 description mentions no parameters, while the schema has 1 parameter ('items') with 0% description coverage. Since schema_description_coverage is 0%, the description should compensate but doesn't, leaving parameters undocumented. However, with only 1 parameter, the baseline is slightly higher than for multiple undocumented parameters.

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 action ('Create new sections') and resource ('in Todoist'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'create_projects' or 'create_tasks', which would require more specificity about what sections are in Todoist's hierarchy.

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 'create_projects' or 'create_tasks'. It doesn't mention prerequisites (e.g., needing an existing project), exclusions, or typical use cases, leaving the agent to infer context from sibling tool names 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/stanislavlysenko0912/todoist-mcp-server'

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