Skip to main content
Glama

get_tasks

Retrieve tasks from a specified ClickUp list, with options to include closed tasks, subtasks, and custom ordering.

Instructions

Get tasks from a ClickUp list. Returns task details including name, description, assignees, and status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesThe ID of the list to get tasks from
include_closedNoWhether to include closed tasks
subtasksNoWhether to include subtasks in the results
pageNoThe page number to get
order_byNoThe field to order by
reverseNoWhether to reverse the order

Implementation Reference

  • The MCP tool handler for 'get_tasks' - registers the tool with name, description, Zod schema for parameters (list_id, include_closed, subtasks, page, order_by, reverse), and the async handler that calls tasksClient.getTasksFromList() and returns the result as JSON text content.
    // Task tools
    server.tool(
      'get_tasks',
      'Get tasks from a ClickUp list. Returns task details including name, description, assignees, and status.',
      {
        list_id: z.string().describe('The ID of the list to get tasks from'),
        include_closed: z.boolean().optional().describe('Whether to include closed tasks'),
        subtasks: z.boolean().optional().describe('Whether to include subtasks in the results'),
        page: z.number().optional().describe('The page number to get'),
        order_by: z.string().optional().describe('The field to order by'),
        reverse: z.boolean().optional().describe('Whether to reverse the order')
      },
      async ({ list_id, ...params }) => {
        try {
          const result = await tasksClient.getTasksFromList(list_id, params);
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error getting tasks:', error);
          return {
            content: [{ type: 'text', text: `Error getting tasks: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • The GetTasksParams TypeScript interface defining the input shape for the underlying API call - includes optional filtering fields like page, order_by, reverse, subtasks, statuses, include_closed, assignees, date ranges, and custom_fields.
    export interface GetTasksParams {
      page?: number;
      order_by?: string;
      reverse?: boolean;
      subtasks?: boolean;
      statuses?: string[];
      include_closed?: boolean;
      assignees?: number[];
      due_date_gt?: number;
      due_date_lt?: number;
      date_created_gt?: number;
      date_created_lt?: number;
      date_updated_gt?: number;
      date_updated_lt?: number;
      custom_fields?: Array<{
        field_id: string;
        operator: string;
        value: any;
      }>;
    }
  • The tool is registered via server.tool('get_tasks', ...) inside setupTaskTools(), which is called from src/index.ts line 42.
    // Task tools
    server.tool(
      'get_tasks',
      'Get tasks from a ClickUp list. Returns task details including name, description, assignees, and status.',
      {
        list_id: z.string().describe('The ID of the list to get tasks from'),
        include_closed: z.boolean().optional().describe('Whether to include closed tasks'),
        subtasks: z.boolean().optional().describe('Whether to include subtasks in the results'),
        page: z.number().optional().describe('The page number to get'),
        order_by: z.string().optional().describe('The field to order by'),
        reverse: z.boolean().optional().describe('Whether to reverse the order')
      },
      async ({ list_id, ...params }) => {
        try {
          const result = await tasksClient.getTasksFromList(list_id, params);
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error getting tasks:', error);
          return {
            content: [{ type: 'text', text: `Error getting tasks: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • The getTasksFromList method on TasksClient - the underlying API helper that performs a GET request to /list/{listId}/task with optional query parameters.
    async getTasksFromList(listId: string, params?: GetTasksParams): Promise<{ tasks: Task[] }> {
      return this.client.get(`/list/${listId}/task`, params);
    }
Behavior2/5

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

Without annotations, the description bears full responsibility for behavioral disclosure. It only notes that it returns task details with certain fields, but omits critical behaviors like pagination (implied by 'page' param but not explained), rate limits, idempotency, or authentication scope. This is minimal disclosure.

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 concise sentence (13 words) with the verb first. Every word adds value, no repetition, and it is efficiently front-loaded. It earns its place without excess.

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?

Given the tool has 6 parameters, no output schema, and no annotations, the description is insufficient for an agent to fully understand invocation context. Missing details: return format, pagination behavior, error handling, and filter/order specifics. The description only covers the tip of the iceberg.

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 coverage is 100% with descriptions for all 6 parameters. The description adds marginal value by mentioning returned fields but does not elaborate on parameter semantics (e.g., valid values for 'order_by' or behavior of 'reverse'). Baseline is 3 due to high schema coverage.

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 action ('Get tasks'), the resource ('from a ClickUp list'), and what is returned (task details with specific fields: name, description, assignees, status). This is specific and distinguishes from sibling tools like 'add_task_to_list' or 'get_task_details'.

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 provides no guidance on when to use this tool versus its many siblings (e.g., 'get_task_details' for a single task, 'add_task_to_list' for modifying). There is no mention of exclusions or prerequisites, leaving the agent to infer usage from the name alone.

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