Skip to main content
Glama

update_checklist

Update the name of an existing ClickUp checklist by providing its ID and new name.

Instructions

Update an existing ClickUp checklist's name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checklist_idYesThe ID of the checklist to update
nameYesThe new name of the checklist

Implementation Reference

  • The tool handler for 'update_checklist'. Uses server.tool() to register the tool with name 'update_checklist', accepts 'checklist_id' and 'name' as Zod-validated string parameters, and calls checklistsClient.updateChecklist() to update the checklist via the ClickUp API. Returns the updated checklist JSON or an error message.
    // Register update_checklist tool
    server.tool(
      'update_checklist',
      'Update an existing ClickUp checklist\'s name.',
      {
        checklist_id: z.string().describe('The ID of the checklist to update'),
        name: z.string().describe('The new name of the checklist')
      },
      async ({ checklist_id, name }) => {
        try {
          const checklist = await checklistsClient.updateChecklist(checklist_id, { name });
          
          return {
            content: [{ type: 'text', text: JSON.stringify(checklist, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error updating checklist:', error);
          return {
            content: [{ type: 'text', text: `Error updating checklist: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • The UpdateChecklistParams interface defines the schema for updating a checklist: it requires a 'name' string.
    export interface UpdateChecklistParams {
      name: string;
    }
  • The ChecklistsClient.updateChecklist() method sends a PUT request to /checklist/{checklistId} with the update parameters, delegating to the underlying ClickUpClient.
    async updateChecklist(checklistId: string, params: UpdateChecklistParams): Promise<Checklist> {
      return this.client.put(`/checklist/${checklistId}`, params);
    }
  • src/index.ts:40-47 (registration)
    The root-level registration call: setupChecklistTools(this.server) is invoked inside ClickUpServer.setupTools(), which is called from the constructor.
    private setupTools() {
      // Set up all tools
      setupTaskTools(this.server);
      setupDocTools(this.server);
      setupSpaceTools(this.server);
      setupChecklistTools(this.server);
      setupCommentTools(this.server);
    }
Behavior2/5

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

No annotations provided; description solely states 'Update' but omits crucial behavioral details such as idempotency, required permissions, error handling (e.g., non-existent checklist), and side effects.

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?

Single sentence, 6 words, front-loaded with the primary action. No extraneous information—every word earns its place.

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?

For a simple two-parameter update tool, the description covers basic purpose but lacks behavioral context (e.g., idempotency, error states). Output schema absent, but not required. Overall adequate but not complete.

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 description coverage is 100%, so baseline is 3. The description merely repeats the 'name' parameter without adding new meaning or format constraints beyond what the schema already provides.

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 explicitly states 'Update an existing ClickUp checklist's name,' providing a specific verb and resource. It clearly distinguishes from sibling tools like create_checklist and delete_checklist.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

No guidance on when to use this tool versus alternatives like update_checklist_item. Implied usage for renaming checklists, but no explicit context or exclusions.

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