Skip to main content
Glama

create_checklist_item

Add a new item to a ClickUp checklist. Optionally assign a user or mark it as resolved.

Instructions

Create a new item in a ClickUp checklist. Supports optional assignee and resolved status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checklist_idYesThe ID of the checklist to create the item in
nameYesThe name of the checklist item
assigneeNoThe ID of the user to assign to the checklist item
resolvedNoWhether the checklist item is resolved

Implementation Reference

  • The MCP tool handler for 'create_checklist_item'. It defines the Zod schema (checklist_id, name, assignee, resolved), builds params, calls the client, and returns the result.
    // Register create_checklist_item tool
    server.tool(
      'create_checklist_item',
      'Create a new item in a ClickUp checklist. Supports optional assignee and resolved status.',
      {
        checklist_id: z.string().describe('The ID of the checklist to create the item in'),
        name: z.string().describe('The name of the checklist item'),
        assignee: z.number().optional().describe('The ID of the user to assign to the checklist item'),
        resolved: z.boolean().optional().describe('Whether the checklist item is resolved')
      },
      async ({ checklist_id, name, assignee, resolved }) => {
        try {
          const itemParams: CreateChecklistItemParams = { name };
          if (assignee !== undefined) itemParams.assignee = assignee;
          if (resolved !== undefined) itemParams.resolved = resolved;
          
          const checklistItem = await checklistsClient.createChecklistItem(checklist_id, itemParams);
          
          return {
            content: [{ type: 'text', text: JSON.stringify(checklistItem, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error creating checklist item:', error);
          return {
            content: [{ type: 'text', text: `Error creating checklist item: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • TypeScript interface CreateChecklistItemParams defining the input schema for creating a checklist item (name required, assignee and resolved optional).
    export interface CreateChecklistItemParams {
      name: string;
      assignee?: number;
      resolved?: boolean;
    }
  • TypeScript interface ChecklistItem defining the output/response shape for a checklist item.
    export interface ChecklistItem {
      id: string;
      name: string;
      orderindex: number;
      resolved: boolean;
      assignee: {
        id: number;
        username: string;
        email: string;
      } | null;
      parent: string | null;
    }
  • Registration of the 'create_checklist_item' tool via server.tool() with its schema and handler.
    // Register create_checklist_item tool
    server.tool(
      'create_checklist_item',
      'Create a new item in a ClickUp checklist. Supports optional assignee and resolved status.',
      {
        checklist_id: z.string().describe('The ID of the checklist to create the item in'),
        name: z.string().describe('The name of the checklist item'),
        assignee: z.number().optional().describe('The ID of the user to assign to the checklist item'),
        resolved: z.boolean().optional().describe('Whether the checklist item is resolved')
      },
      async ({ checklist_id, name, assignee, resolved }) => {
        try {
          const itemParams: CreateChecklistItemParams = { name };
          if (assignee !== undefined) itemParams.assignee = assignee;
          if (resolved !== undefined) itemParams.resolved = resolved;
          
          const checklistItem = await checklistsClient.createChecklistItem(checklist_id, itemParams);
          
          return {
            content: [{ type: 'text', text: JSON.stringify(checklistItem, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error creating checklist item:', error);
          return {
            content: [{ type: 'text', text: `Error creating checklist item: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • The underlying client method createChecklistItem that sends a POST request to /checklist/{checklistId}/checklist_item with the params.
    async createChecklistItem(checklistId: string, params: CreateChecklistItemParams): Promise<ChecklistItem> {
      return this.client.post(`/checklist/${checklistId}/checklist_item`, params);
    }
Behavior2/5

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

No annotations provided, and the description only mentions optional fields. It does not disclose behaviors like idempotency, side effects, error conditions, or authentication requirements.

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 sentences, front-loaded with purpose, no unnecessary words. Highly efficient.

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 creation tool with a fully described schema, but lacks information about return values or error cases. Could be improved with additional behavioral context.

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 has 100% description coverage, so the description adds minimal value. It reinforces that assignee and resolved are optional but does not clarify their format or constraints beyond the schema.

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 the action (create), resource (item in a ClickUp checklist), and optional fields (assignee, resolved). Effectively distinguishes from sibling tools like create_checklist and update_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 explicit guidance on when to use this tool vs alternatives. The description does not mention prerequisites, exclusions, or comparison with sibling tools.

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