Skip to main content
Glama

remove_task_from_list

Remove a task from a ClickUp list without deleting it, allowing reassignment to another list.

Instructions

Remove a task from a ClickUp list without deleting the task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesThe ID of the list to remove the task from
task_idYesThe ID of the task to remove

Implementation Reference

  • MCP tool handler that defines and registers 'remove_task_from_list' with Zod schema for list_id and task_id, calls the listsClient.removeTaskFromList method, and returns the result as JSON text content.
    server.tool(
      'remove_task_from_list',
      'Remove a task from a ClickUp list without deleting the task.',
      {
        list_id: z.string().describe('The ID of the list to remove the task from'),
        task_id: z.string().describe('The ID of the task to remove')
      },
      async ({ list_id, task_id }) => {
        try {
          const result = await listsClient.removeTaskFromList(list_id, task_id);
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error removing task from list:', error);
          return {
            content: [{ type: 'text', text: `Error removing task from list: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • Zod schema defining the input parameters for the remove_task_from_list tool: list_id (string) and task_id (string).
    {
      list_id: z.string().describe('The ID of the list to remove the task from'),
      task_id: z.string().describe('The ID of the task to remove')
  • Registration of the 'remove_task_from_list' tool on the MCP server via server.tool(), which defines the name, description, input schema, and handler.
    server.tool(
      'remove_task_from_list',
      'Remove a task from a ClickUp list without deleting the task.',
      {
        list_id: z.string().describe('The ID of the list to remove the task from'),
        task_id: z.string().describe('The ID of the task to remove')
      },
      async ({ list_id, task_id }) => {
        try {
          const result = await listsClient.removeTaskFromList(list_id, task_id);
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error removing task from list:', error);
          return {
            content: [{ type: 'text', text: `Error removing task from list: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • ListsClient method that performs the actual API call: HTTP DELETE to /list/{listId}/task/{taskId} to remove a task from a ClickUp list.
    async removeTaskFromList(listId: string, taskId: string): Promise<{ success: boolean }> {
      return this.client.delete(`/list/${listId}/task/${taskId}`);
    }
Behavior3/5

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

The description clarifies that the task is not deleted, which adds value beyond the input schema. However, it does not disclose other behavioral traits such as permission requirements, effect on task visibility, or whether the task is removed from all lists. With no annotations, the description bears full responsibility but only partially fulfills it.

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?

The description is a single, well-structured sentence that conveys the essential information without superfluous words. It is front-loaded and immediately understandable.

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

Completeness4/5

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

For a simple tool with two required parameters and no output schema, the description is mostly complete. It could additionally mention that the task remains in the workspace or other lists, but it covers the core behavior adequately.

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% description coverage, providing clear definitions for 'list_id' and 'task_id'. The tool description adds no additional meaning beyond the schema, so the baseline score of 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 the specific action: removing a task from a list without deleting it. It uses a specific verb ('remove') and resource ('task from a ClickUp list'), and distinguishes from sibling tools that delete or add tasks.

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 like 'delete_task' or 'add_task_to_list'. There is no mention of prerequisites, exclusions, or context that would help an agent decide appropriately.

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