Skip to main content
Glama

create_checklist

Add a new checklist to any ClickUp task by specifying the task ID and checklist name. Returns the created checklist details.

Instructions

Create a new checklist in a ClickUp task. Returns the created checklist details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesThe ID of the task to create the checklist in
nameYesThe name of the checklist

Implementation Reference

  • Registration of the 'create_checklist' tool on the MCP server via server.tool(), with Zod schema for task_id and name inputs, and the async handler that calls checklistsClient.createChecklist().
    server.tool(
      'create_checklist',
      'Create a new checklist in a ClickUp task. Returns the created checklist details.',
      {
        task_id: z.string().describe('The ID of the task to create the checklist in'),
        name: z.string().describe('The name of the checklist')
      },
      async ({ task_id, name }) => {
        try {
          const checklist = await checklistsClient.createChecklist(task_id, { name } as CreateChecklistParams);
          
          return {
            content: [{ type: 'text', text: JSON.stringify(checklist, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error creating checklist:', error);
          return {
            content: [{ type: 'text', text: `Error creating checklist: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • The async handler function for 'create_checklist' - extracts task_id and name, calls checklistsClient.createChecklist(), returns the result as JSON text, and handles errors.
    async ({ task_id, name }) => {
      try {
        const checklist = await checklistsClient.createChecklist(task_id, { name } as CreateChecklistParams);
        
        return {
          content: [{ type: 'text', text: JSON.stringify(checklist, null, 2) }]
        };
      } catch (error: any) {
        console.error('Error creating checklist:', error);
        return {
          content: [{ type: 'text', text: `Error creating checklist: ${error.message}` }],
          isError: true
        };
      }
    }
  • CreateChecklistParams interface defining the input shape (name: string) for creating a checklist.
    export interface CreateChecklistParams {
      name: string;
      // Note: The ClickUp API doesn't support creating items when creating a checklist
      // Items must be created separately using the createChecklistItem method
    }
  • The createChecklist method in ChecklistsClient class that sends a POST request to /task/{taskId}/checklist with the params.
    async createChecklist(taskId: string, params: CreateChecklistParams): Promise<Checklist> {
      return this.client.post(`/task/${taskId}/checklist`, params);
    }
  • src/index.ts:7-7 (registration)
    Import of setupChecklistTools from the checklist-tools module.
    import { setupChecklistTools } from './tools/checklist-tools.js';
Behavior2/5

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

With no annotations, the description only states 'creates' and 'returns details'. It does not disclose side effects, idempotency, permissions, or error conditions, which is insufficient for a write operation.

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?

Two concise sentences with no unnecessary words. Front-loaded with the purpose.

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?

The tool is simple with 2 parameters and no output schema, but the description lacks usage guidelines and behavioral details. It is minimally adequate but could mention failure scenarios.

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 parameter descriptions (task_id and name). The description adds no extra meaning beyond the schema, so baseline 3 applies.

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 'Create', the resource 'a new checklist in a ClickUp task', and the return value 'Returns the created checklist details.' It is specific and distinguishable from sibling tools like create_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 Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, such as create_checklist_item or update_checklist. It does not mention prerequisites like the task must exist or when not to use it.

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