Skip to main content
Glama
Sign In
ClickUp MCP Server

ClickUp MCP Server

by azukhrufy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

edit_checklist

Rename a ClickUp checklist by specifying its ID and the new name.

Instructions

Edit a ClickUp checklist.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "checklist_id": "<checklist_id>"
    },
    "name": "edit_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew name of the checklist
checklist_idYesThe ID of the checklist

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior1/5

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

With no annotations and no output schema, the description carries the full burden of behavioral disclosure. 'Edit' is vague—it doesn't say whether editing affects items, requires permissions, is reversible, or what response is expected. The tool's behavior remains completely opaque.

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

Conciseness4/5

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

The description is a single concise sentence with no redundant words. It is front-loaded and easily readable, though it sacrifices depth for brevity. Given the tool's simplicity, the conciseness is effective, but it's not exceptional.

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

Completeness2/5

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

The tool has a simple schema and no annotations or output schema, so the description needs to provide more behavioral context. The description only states the high-level purpose, leaving out any details about side effects, permissions, or return values. This is insufficient for an agent to reliably invoke the tool.

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?

The input schema has 100% coverage for both parameters (checklist_id and name) with clear descriptions. The description adds no additional meaning beyond the schema, so a baseline of 3 is appropriate because the schema already documents the necessary semantics.

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 ('Edit') and the resource ('ClickUp checklist'). It distinguishes the tool from siblings like create_checklist and delete_checklist by action, though it doesn't specify what 'edit' entails (e.g., renaming). The clarity is adequate but doesn't differentiate beyond the verb.

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?

The description gives no guidance on when to use this tool versus alternatives, such as create_checklist or update_checklist_item. It doesn't mention contexts, prerequisites, or why you would choose edit_checklist over related checklist/item tools. This is a complete absence of usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools