Skip to main content
Glama

update_list

Rename a ClickUp list by providing its ID and the new name.

Instructions

Update an existing ClickUp list's name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesThe ID of the list to update
nameYesThe new name of the list

Implementation Reference

  • The 'update_list' tool handler registered on the McpServer. It accepts list_id and name as input (Zod-validated), calls listsClient.updateList(), and returns the result as JSON text. Error handling is included.
    server.tool(
      'update_list',
      'Update an existing ClickUp list\'s name.',
      {
        list_id: z.string().describe('The ID of the list to update'),
        name: z.string().describe('The new name of the list')
      },
      async ({ list_id, name }) => {
        try {
          const result = await listsClient.updateList(list_id, { name });
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error updating list:', error);
          return {
            content: [{ type: 'text', text: `Error updating list: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • The ListsClient.updateList() method that makes an HTTP PUT request to /list/{listId} with the update params.
    async updateList(listId: string, params: UpdateListParams): Promise<List> {
      return this.client.put(`/list/${listId}`, params);
    }
  • The UpdateListParams interface defining the shape of the update parameters (name is optional).
    export interface UpdateListParams {
      name?: string;
      // ...other parameters for updating a list...
    }
  • The Zod schema for the 'update_list' tool defining the required input fields: list_id (string) and name (string).
    {
      list_id: z.string().describe('The ID of the list to update'),
      name: z.string().describe('The new name of the list')
    },
  • The setupTaskTools function that registers all tools (including 'update_list') on the McpServer.
    export function setupTaskTools(server: McpServer): void {
Behavior2/5

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

With no annotations, the description carries the full burden. It only states mutation ('update'), but lacks disclosure on side effects, failure scenarios, authentication needs, or return behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short, but for a simple two-parameter tool it is acceptable. However, it could be more informative without being verbose.

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 low complexity, 2 required params, and no output schema, the description is somewhat complete but lacks mention of return value or errors, which would help an agent.

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 adds no extra meaning beyond the schema (e.g., explanation of list_id or name format), providing no additional value.

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 verb 'update' and the resource 'existing ClickUp list's name', which is specific and not a tautology. It differentiates from sibling tools that create, delete, or retrieve lists.

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 when updating other list attributes beyond name. The description does not mention limitations or prerequisites.

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