Skip to main content
Glama

delete_list

Remove a ClickUp list and all its tasks. Permanently delete any list by providing its ID.

Instructions

Delete a list from ClickUp. Removes the list and its tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesThe ID of the list to delete

Implementation Reference

  • Registration of the 'delete_list' MCP tool with input schema (list_id) and handler that calls listsClient.deleteList
    server.tool(
      'delete_list',
      'Delete a list from ClickUp. Removes the list and its tasks.',
      {
        list_id: z.string().describe('The ID of the list to delete')
      },
      async ({ list_id }) => {
        try {
          const result = await listsClient.deleteList(list_id);
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error deleting list:', error);
          return {
            content: [{ type: 'text', text: `Error deleting list: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • Input schema for delete_list: expects a single string parameter 'list_id'
    {
      list_id: z.string().describe('The ID of the list to delete')
    },
  • The ListsClient.deleteList method that performs the actual HTTP DELETE to the ClickUp API endpoint /list/{listId}
    async deleteList(listId: string): Promise<{ success: boolean }> {
      return this.client.delete(`/list/${listId}`);
    }
  • The underlying HTTP DELETE method on ClickUpClient that makes the actual axios call
    async delete<T = any>(endpoint: string): Promise<T> {
      const response = await this.axiosInstance.delete(endpoint);
      return response.data;
    }
Behavior2/5

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

Discloses task removal but lacks info on irreversibility, required permissions, or error conditions. No annotations to supplement.

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?

Single sentence that efficiently conveys action and consequence. Could front-load cascade behavior, but still concise.

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

Completeness3/5

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

Adequate for a simple delete with one param and no output schema, but lacks context on idempotency, side effects, or success/error responses.

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 covers the sole parameter with description. Description adds no extra meaning. Baseline 3 due to 100% schema coverage.

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?

Clearly states verb 'Delete', resource 'list', and cascading effect on tasks. Distinguishes from siblings like create_list or update_list.

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 on when to use this vs other deletion tools like delete_folder or delete_comment. No prerequisites or alternatives 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