Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_remove_task_from_list

DestructiveIdempotent

Remove a task from a secondary list while preserving its membership in the home list. Requires the Tasks in Multiple Lists ClickApp to be enabled.

Instructions

Remove a Task's membership from an additional (non-home) List.

Requires the Tasks in Multiple Lists ClickApp to be enabled; without it ClickUp returns 403. You cannot remove a Task from its primary (home) List this way — only from additional Lists it was added to via clickup_add_task_to_list.

When to Use:

  • Undoing a clickup_add_task_to_list call, or cleaning up a Task that no longer needs to appear in a secondary List.

When NOT to Use:

  • Removing a Task entirely from its home List — that requires deleting the Task (see the tasks module) rather than this membership removal.

Returns: A confirmation string, or an Error ... string.

Examples: params = {"list_id": "901300123456", "task_id": "abc123"}

Error Handling: 403 means the Tasks in Multiple Lists ClickApp is not enabled, or you tried to remove the Task from its home List. 404 means list_id or task_id does not exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond annotations (destructive, idempotent), description discloses prerequisite (Tasks in Multiple Lists ClickApp), error handling (403, 404), and return type (confirmation/error string). No contradictions.

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?

Well-structured with clear sections, front-loaded main action, no redundancy. Every sentence earns its place.

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?

Given annotations, output schema exists, and tool complexity, description covers prerequisites, usage boundaries, error handling, and example. Complete for agent decision-making.

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?

Despite schema description coverage of 0%, the description provides examples and context for parameters, though the schema itself contains descriptions. Adds value with concrete example and error implications.

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 the tool removes a task's membership from an additional (non-home) list, using specific verbs and resources. It distinguishes from deleting a task entirely and from removing from the home list.

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' (undoing add_task_to_list) and 'when NOT to use' (removing from home list) sections, including alternatives like deleting the task.

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