Skip to main content
Glama

update_checklist_item

Update a ClickUp checklist item's name, assignee, or resolved status by specifying the checklist and item IDs.

Instructions

Update an existing ClickUp checklist item's properties including name, assignee, and resolved status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checklist_idYesThe ID of the checklist containing the item
checklist_item_idYesThe ID of the checklist item to update
nameNoThe new name of the checklist item
assigneeNoThe ID of the user to assign to the checklist item
resolvedNoWhether the checklist item is resolved

Implementation Reference

  • Tool registration and handler for 'update_checklist_item'. Defines the tool with Zod schema params (checklist_id, checklist_item_id, optional name/assignee/resolved), and the handler that calls checklistsClient.updateChecklistItem() and returns the result.
    // Register update_checklist_item tool
    server.tool(
      'update_checklist_item',
      'Update an existing ClickUp checklist item\'s properties including name, assignee, and resolved status.',
      {
        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 update'),
        name: z.string().optional().describe('The new 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, checklist_item_id, name, assignee, resolved }) => {
        try {
          const itemParams: UpdateChecklistItemParams = {};
          if (name !== undefined) itemParams.name = name;
          if (assignee !== undefined) itemParams.assignee = assignee;
          if (resolved !== undefined) itemParams.resolved = resolved;
          
          const checklistItem = await checklistsClient.updateChecklistItem(checklist_id, checklist_item_id, itemParams);
          
          return {
            content: [{ type: 'text', text: JSON.stringify(checklistItem, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error updating checklist item:', error);
          return {
            content: [{ type: 'text', text: `Error updating checklist item: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • TypeScript interface for update checklist item parameters: all optional fields (name, assignee, resolved).
    export interface UpdateChecklistItemParams {
      name?: string;
      assignee?: number;
      resolved?: boolean;
    }
  • The API client method that sends a PUT request to /checklist/{checklistId}/checklist_item/{checklistItemId} to update the checklist item.
    async updateChecklistItem(checklistId: string, checklistItemId: string, params: UpdateChecklistItemParams): Promise<ChecklistItem> {
      return this.client.put(`/checklist/${checklistId}/checklist_item/${checklistItemId}`, params);
    }
  • src/index.ts:40-47 (registration)
    Server entry point: calls setupChecklistTools(server) which registers 'update_checklist_item' among other checklist tools.
    private setupTools() {
      // Set up all tools
      setupTaskTools(this.server);
      setupDocTools(this.server);
      setupSpaceTools(this.server);
      setupChecklistTools(this.server);
      setupCommentTools(this.server);
    }
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that updates affect 'name, assignee, and resolved status', implying other properties are unchanged, but does not confirm whether partial updates are allowed or if any side effects occur. It also does not mention authentication prerequisites or potential errors.

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 a single sentence of 13 words, directly stating the action and key updatable properties. No filler or redundancy, making it highly efficient and easy to parse.

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?

Given the five parameters (two required, three optional) and no output schema or annotations, the description provides a reasonable overview but lacks detail on how optional fields behave (e.g., set vs. unset), error states, or the effect of not including optional fields. It is minimally adequate but could be more informative.

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%, so baseline is 3. The description lists three of the optional parameters (name, assignee, resolved) but adds no new meaning beyond what the schema already provides (e.g., types, required fields). The description does not clarify that only provided optional fields will be updated.

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

Purpose4/5

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

The description clearly states the action ('Update'), the resource ('checklist item'), and lists the updatable properties ('name, assignee, and resolved status'). It distinguishes from sibling tools like create_checklist_item or delete_checklist_item by implying modification, but does not explicitly differentiate from update_checklist, which updates the parent checklist instead.

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 versus alternatives. The description implies it is for modifying an existing item, but does not state when not to use it (e.g., for creating new items) or suggest sibling tools like create_checklist_item for creation.

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