Skip to main content
Glama

delete_projects

Remove projects from Todoist by specifying their ID or name to clean up your workspace and manage task organization.

Instructions

Delete projects from Todoist Either 'id' or the 'name' to identify the target.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes

Implementation Reference

  • Core handler logic for batch delete_projects tool: fetches projects list if name lookup needed, resolves project ID by name, validates and encodes ID for path '/projects/{id}', executes todoistApi.delete(finalPath), returns batched results with success summary.
    const handler = async (args: z.infer<typeof batchSchema>): Promise<any> => {
        const { items } = args;
    
        // For modes other than create, check if name lookup is needed
        let allItems: any[] = [];
    
        const needsNameLookup =
            options.mode !== 'create' &&
            options.nameField &&
            options.findByName &&
            items.some(item => item[options.nameField!] && !item[options.idField!]);
    
        if (needsNameLookup) {
            // Determine the base path for fetching all items
            // Example: /tasks from /tasks/{id}
            const lookupPath =
                options.basePath || (options.path ? options.path.split('/{')[0] : '');
            allItems = await todoistApi.get(lookupPath, {});
        }
    
        const results = await Promise.all(
            items.map(async item => {
                if (options.validateItem) {
                    const validation = options.validateItem(item);
    
                    if (!validation.valid) {
                        return {
                            success: false,
                            error: validation.error || 'Validation failed',
                            item,
                        };
                    }
                }
    
                try {
                    let finalPath = '';
                    const apiParams = { ...item };
    
                    // For modes where need id
                    if (options.mode !== 'create' && options.idField) {
                        let itemId = item[options.idField];
                        let matchedName = null;
                        let matchedContent = null;
    
                        // If no ID but name is provided, search by name
                        if (!itemId && item[options.nameField!] && options.findByName) {
                            const searchName = item[options.nameField!];
                            const matchedItem = options.findByName(searchName, allItems);
    
                            if (!matchedItem) {
                                return {
                                    success: false,
                                    error: `Item not found with name: ${searchName}`,
                                    item,
                                };
                            }
    
                            itemId = matchedItem.id;
                            matchedName = searchName;
                            matchedContent = matchedItem.content;
                        }
    
                        if (!itemId) {
                            return {
                                success: false,
                                error: `Either ${options.idField} or ${options.nameField} must be provided`,
                                item,
                            };
                        }
    
                        // Apply security validation to itemId before using in path
                        const safeItemId = validatePathParameter(itemId, options.idField || 'id');
    
                        if (options.basePath && options.pathSuffix) {
                            finalPath = `${options.basePath}${options.pathSuffix.replace('{id}', safeItemId)}`;
                        } else if (options.path) {
                            finalPath = options.path.replace('{id}', safeItemId);
                        }
    
                        delete apiParams[options.idField];
                        if (options.nameField) {
                            delete apiParams[options.nameField];
                        }
    
                        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;
                        }
    
                        const response: any = {
                            success: true,
                            id: itemId,
                            result,
                        };
    
                        if (matchedName) {
                            response.found_by_name = matchedName;
                            response.matched_content = matchedContent;
                        }
    
                        return response;
                    }
                    // 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,
                        };
                    }
                } catch (error) {
                    return {
                        success: false,
                        error: error instanceof Error ? error.message : String(error),
                        item,
                    };
                }
            })
        );
    
        const successCount = results.filter(r => r.success).length;
        return {
            success: successCount === items.length,
            summary: {
                total: items.length,
                succeeded: successCount,
                failed: items.length - successCount,
            },
            results,
        };
    };
  • Tool registration for 'delete_projects': configures batch handler with schema (id or name), DELETE method to '/projects/{id}', delete mode, name-based lookup.
    createBatchApiHandler({
        name: 'delete_projects',
        description: 'Delete projects from Todoist',
        itemSchema: {
            id: z.string().optional().describe('ID of the project to delete (preferred over name)'),
            name: z.string().optional().describe('Name of the project to delete'),
        },
        method: 'DELETE',
        path: '/projects/{id}',
        mode: 'delete',
        idField: 'id',
        nameField: 'name',
        findByName: (name, items) =>
            items.find(item => item.name.toLowerCase().includes(name.toLowerCase())),
    });
  • Input schema for delete_projects: optional project id (preferred) or name.
    itemSchema: {
        id: z.string().optional().describe('ID of the project to delete (preferred over name)'),
        name: z.string().optional().describe('Name of the project to delete'),
    },
  • createHandler helper: wraps the tool handler, handles errors, formats output, and registers the tool with MCP server.tool(name, description, schema, callback). Called by createBatchApiHandler.
    export function createHandler<T extends z.ZodRawShape>(
        name: string,
        description: string,
        paramsSchema: T,
        handler: (args: HandlerArgs<T>) => Promise<any>
    ): void {
        const mcpToolCallback = async (args: HandlerArgs<T>): Promise<CallToolResult> => {
            try {
                const result = await handler(args);
    
                return {
                    content: [
                        {
                            type: 'text',
                            text: JSON.stringify(result ?? null, null, 2).trim(),
                        },
                    ],
                };
            } catch (error) {
                const errorMessage = error instanceof Error ? error.message : String(error);
    
                console.error(`Error in tool ${name}:`, error);
    
                return {
                    isError: true,
                    content: [
                        {
                            type: 'text',
                            text: `Error executing tool '${name}': ${errorMessage}`,
                        },
                    ],
                };
            }
        };
    
        // Crazy cast, if you can do it better, please, let me knows
        server.tool(name, description, paramsSchema, mcpToolCallback as unknown as ToolCallback<T>);
    }
  • createBatchApiHandler calls createHandler to register the generated batch handler for delete_projects.
        return createHandler(options.name, finalDescription, batchSchema.shape, handler);
    }
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. It states 'Delete' which implies a destructive mutation, but doesn't disclose critical behaviors: whether deletion is permanent/reversible, authentication requirements, rate limits, error handling, or what happens to associated data (e.g., tasks in deleted projects). This leaves significant gaps for safe agent operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief and front-loaded with the core action. Both sentences are necessary: the first states the purpose, the second explains parameter usage. No wasted words, though it could be more structured (e.g., bullet points for behaviors).

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 destructive mutation tool with no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks behavioral context (permanence, side effects), error information, and output expectations. Given the complexity and risk of deletion, this is inadequate for safe agent invocation.

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?

Schema description coverage is 0%, so the description must compensate. It explains that either 'id' or 'name' can identify targets, and implies 'id' is preferred, adding meaningful semantics beyond the bare schema. However, it doesn't clarify the 'items' array structure or constraints (e.g., bulk deletion limits).

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 ('Delete') and resource ('projects from Todoist'), making the purpose unambiguous. It distinguishes from siblings like 'delete_tasks' or 'delete_comments' by specifying the resource type. However, it doesn't explicitly differentiate from 'move_projects' or 'update_projects' in terms of destructive nature.

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 'move_projects' or 'update_projects', nor does it mention prerequisites (e.g., authentication needs) or consequences. It only explains parameter identification, not contextual usage.

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