Skip to main content
Glama

delete_checklist_item

Remove a specific item from a checklist by providing the checklist ID and item ID.

Instructions

Delete an item from a ClickUp checklist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checklist_idYesThe ID of the checklist containing the item
checklist_item_idYesThe ID of the checklist item to delete

Implementation Reference

  • Registration of the 'delete_checklist_item' tool with Zod schema for checklist_id and checklist_item_id. Calls checklistsClient.deleteChecklistItem.
    // Register delete_checklist_item tool
    server.tool(
      'delete_checklist_item',
      'Delete an item from a ClickUp checklist.',
      {
        checklist_id: z.string().describe('The ID of the checklist containing the item'),
        checklist_item_id: z.string().describe('The ID of the checklist item to delete')
      },
      async ({ checklist_id, checklist_item_id }) => {
        try {
          const result = await checklistsClient.deleteChecklistItem(checklist_id, checklist_item_id);
          
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error deleting checklist item:', error);
          return {
            content: [{ type: 'text', text: `Error deleting checklist item: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • Handler function for delete_checklist_item that takes checklist_id and checklist_item_id, calls the client method, and returns the result as JSON.
    async ({ checklist_id, checklist_item_id }) => {
      try {
        const result = await checklistsClient.deleteChecklistItem(checklist_id, checklist_item_id);
        
        return {
          content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
        };
      } catch (error: any) {
        console.error('Error deleting checklist item:', error);
        return {
          content: [{ type: 'text', text: `Error deleting checklist item: ${error.message}` }],
          isError: true
        };
      }
    }
  • The ChecklistsClient.deleteChecklistItem method that performs the actual HTTP DELETE request to /checklist/{checklistId}/checklist_item/{checklistItemId}
    /**
     * Delete a checklist item
     * @param checklistId The ID of the checklist containing the item
     * @param checklistItemId The ID of the checklist item to delete
     * @returns Success message
     */
    async deleteChecklistItem(checklistId: string, checklistItemId: string): Promise<{ success: boolean }> {
      return this.client.delete(`/checklist/${checklistId}/checklist_item/${checklistItemId}`);
    }
  • Zod input schema for delete_checklist_item: requires checklist_id (string) and checklist_item_id (string).
    {
      checklist_id: z.string().describe('The ID of the checklist containing the item'),
      checklist_item_id: z.string().describe('The ID of the checklist item to delete')
    },
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits beyond the delete action. It does not mention irreversibility, side effects, or permission requirements, which are critical for a destructive 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 a single sentence with no fluff. It is concise, though it could benefit from slightly more detail without losing conciseness.

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?

With no annotations and no output schema, the description lacks essential context such as prerequisites, limitations, or behavior on failure. It is minimally complete but insufficient for an agent to use confidently.

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 coverage is 100%: both parameters have descriptions in the input schema. The description adds no extra meaning beyond the schema, so baseline 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 verb 'delete' and the resource 'checklist item', distinguishing it from siblings like delete_checklist (deletes entire checklist) and create_checklist_item (creates). It is specific and unambiguous.

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, no prerequisites, and no conditions under which deletion is allowed or not. It lacks exclusions or context for 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/nsxdavid/clickup-mcp-server'

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