Skip to main content
Glama

delete_checklist

Remove a checklist and all its items from a ClickUp task.

Instructions

Delete a checklist from a ClickUp task. Removes the checklist and all its items.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checklist_idYesThe ID of the checklist to delete

Implementation Reference

  • The handler function that executes the 'delete_checklist' tool logic. It registers the tool with name 'delete_checklist', accepts a 'checklist_id' string parameter, calls the underlying client method, and returns the result as JSON text.
    // Register delete_checklist tool
    server.tool(
      'delete_checklist',
      'Delete a checklist from a ClickUp task. Removes the checklist and all its items.',
      {
        checklist_id: z.string().describe('The ID of the checklist to delete')
      },
      async ({ checklist_id }) => {
        try {
          const result = await checklistsClient.deleteChecklist(checklist_id);
          
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error deleting checklist:', error);
          return {
            content: [{ type: 'text', text: `Error deleting checklist: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • Input schema for the 'delete_checklist' tool, defined using Zod — expects a single required string parameter 'checklist_id'.
    {
      checklist_id: z.string().describe('The ID of the checklist to delete')
  • Registration of the 'delete_checklist' tool via server.tool() on the McpServer instance within the setupChecklistTools function.
    server.tool(
      'delete_checklist',
      'Delete a checklist from a ClickUp task. Removes the checklist and all its items.',
      {
        checklist_id: z.string().describe('The ID of the checklist to delete')
      },
      async ({ checklist_id }) => {
        try {
          const result = await checklistsClient.deleteChecklist(checklist_id);
          
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error deleting checklist:', error);
          return {
            content: [{ type: 'text', text: `Error deleting checklist: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • The underlying API client method 'deleteChecklist' that performs the actual HTTP DELETE request to '/checklist/{checklistId}'. Returns { success: boolean }.
    async deleteChecklist(checklistId: string): Promise<{ success: boolean }> {
      return this.client.delete(`/checklist/${checklistId}`);
    }
  • src/index.ts:45-46 (registration)
    Top-level registration: setupChecklistTools(this.server) is called in the ClickUpServer.setupTools() method, which wires up all checklist tools including 'delete_checklist'.
    setupChecklistTools(this.server);
    setupCommentTools(this.server);
Behavior3/5

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

Since annotations are absent, the description must carry full weight. It states that the checklist and all its items are removed, which is the core behavior. However, it does not explicitly mention irreversibility or any permissions needed, which would enhance transparency.

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 extremely concise: two sentences with no filler. Every word contributes to understanding the tool's purpose and behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple delete operation with full schema coverage and no output schema, the description is nearly complete. It explains what is removed. A minor improvement would be explicitly stating the action is irreversible, but it's already implied.

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 input schema covers 100% of parameters with descriptions. The description adds no additional meaning beyond what the schema provides for the single parameter (checklist_id). Baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the action (Delete), the resource (checklist), and the context (from a ClickUp task). It also mentions that all items are removed, which distinguishes it from sibling tools like delete_checklist_item.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a straightforward purpose but offers no explicit guidance on when to use this tool versus alternatives or when not to use it. The context is clear, but no exclusions or prerequisites 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/nsxdavid/clickup-mcp-server'

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