Skip to main content
Glama

clickup_checklist_update

Rename or reposition a checklist within a task while preserving all checklist items.

Instructions

Rename a checklist or change its position among the task's checklists. Does not affect the checklist's items — use clickup_checklist_update_item / add_item / delete_item for those. Returns the updated checklist object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checklist_idYesID of the checklist to update. Obtain from clickup_task_get (field: checklists[].id).
nameNoNew display name for the checklist. Omit to keep current name.
positionNoZero-indexed position among the task's checklists (0 = first). Omit to keep current position.
Behavior4/5

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

Describes scope clearly (no effect on items). Without annotations, this is good but could mention permissions or 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?

Two sentences front-loading purpose and exclusions. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple update tool, covers purpose, scope, and return. No output schema needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all params fully. Description adds context about what the update does and what it doesn't affect.

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 verb (rename/change position) and resource (checklist). Distinguishes from siblings by specifying what it does not affect.

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

Usage Guidelines5/5

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

Explicitly tells when to use alternative tools for item operations. Also states return value.

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/nicholasbester/clickup-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server