Skip to main content
Glama

get_tasks

Retrieve tasks from a ClickUp list by specifying the list ID and optional limit to manage and organize task data.

Instructions

Get tasks from a ClickUp list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesClickUp List ID
limitNoNumber of tasks to retrieve (max 100)

Implementation Reference

  • The async getTasks function implementing the core logic of the 'get_tasks' tool: fetches tasks from ClickUp API for given list_id (limit optional), formats as JSON, handles Axios errors.
    const getTasks = async (args: any) => {
      try {
        const response = await clickupApi.get(`/list/${args.list_id}/task`, {
          params: {
            limit: args.limit || 50,
          },
        });
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response.data.tasks, null, 2),
            },
          ],
        };
      } catch (error) {
        if (axios.isAxiosError(error)) {
          return {
            content: [
              {
                type: "text",
                text: `ClickUp API error: ${error.response?.data?.err ?? error.message}`,
              },
            ],
            isError: true,
          };
        }
        throw error;
      }
    };
  • Schema definition for the 'get_tasks' tool, specifying input parameters list_id (required) and optional limit.
    get_tasks: {
      description: "Get tasks from a ClickUp list",
      inputSchema: {
        type: "object",
        properties: {
          list_id: {
            type: "string",
            description: "ClickUp List ID"
          },
          limit: {
            type: "number",
            description: "Number of tasks to retrieve (max 100)",
            default: 50,
            minimum: 1,
            maximum: 100
          }
        },
        required: ["list_id"]
      }
    },
  • src/index.ts:279-294 (registration)
    Registration of tool handlers via setRequestHandler for CallToolRequestSchema, including the switch case dispatching 'get_tasks' calls to the getTasks function.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      // @ts-ignore
      const { name, arguments: args } = request.params;
      switch (name) {
        case 'get_tasks':
          return await getTasks(args);
        case 'create_task':
          return await createTask(args);
        case 'update_task':
          return await updateTask(args);
        case 'get_task':
          return await getTask(args);
        default:
          throw new Error(`Unknown tool: ${name}`);
      }
    });
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action without behavioral details. It doesn't disclose if this is read-only (implied but not explicit), rate limits, pagination, error handling, or what the return format looks like (e.g., list of tasks). This is inadequate for a tool with parameters and no output schema.

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, efficient sentence with no wasted words. It's front-loaded and directly states the tool's purpose, making it easy to parse quickly.

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 parameters, no annotations, and no output schema, the description is incomplete. It lacks behavioral context (e.g., read-only confirmation, return format), usage differentiation from siblings, and any mention of limitations like the max limit of 100. This leaves significant gaps for an agent to operate effectively.

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 description coverage is 100%, so parameters are documented in the schema. The description adds no additional meaning beyond implying retrieval from a list, which aligns with the schema. Baseline 3 is appropriate as the schema handles parameter documentation effectively.

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 ('Get') and resource ('tasks from a ClickUp list'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_task' (singular vs. plural) or specify scope (e.g., all tasks vs. filtered), which prevents a perfect score.

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 'get_task' (singular) or 'create_task'. The description implies retrieval but lacks context on prerequisites, such as needing a valid list ID, or exclusions, leaving the agent to infer usage.

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

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