Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_checklist_item

Add a new line item to an existing ClickUp checklist. Provide the checklist ID and item name, with an optional assignee.

Instructions

Add a new line item to an existing checklist.

When to Use:

  • Adding a to-do line to a checklist created with clickup_create_checklist.

When NOT to Use:

  • To create the checklist itself first — use clickup_create_checklist.

Returns: A confirmation string; when the API response includes the new item's id it is included, otherwise only the item name and checklist id are echoed.

Examples: params = {"checklist_id": "b8a8...", "name": "Write tests"} params = {"checklist_id": "b8a8...", "name": "Review PR", "assignee": 183}

Error Handling: 404 means the checklist_id does not exist; 400 for an invalid assignee id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations indicate non-read-only, non-destructive, non-idempotent. The description adds details on return format (confirmation string with optional id) and error handling (404, 400), supplementing annotations well.

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?

Well-structured with clear sections and examples, though slightly verbose. Front-loaded with purpose, but every sentence contributes value.

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?

Covers usage, alternatives, errors, and return format. With a simple schema and output schema provided, the description is sufficiently complete for an agent to use correctly.

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 descriptions already cover parameter meanings. The description's examples illustrate usage but do not add significant semantic depth beyond the schema, so baseline 3 is appropriate.

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 clearly states 'Add a new line item to an existing checklist,' which is a specific verb+resource. It distinguishes from siblings like clickup_create_checklist by focusing on adding an item to an existing checklist.

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?

Explicit 'When to Use' and 'When NOT to Use' sections provide clear context, including naming the alternative tool clickup_create_checklist for creating the checklist itself.

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/trustxai/clickup-mcp'

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