Skip to main content
Glama

clickup

by io.usefulapi

Get tasks

clickup_get_tasks
Read-only

Get the tasks in a list, with optional filters and pagination. ClickUp REST: GET /list/{list_id}/task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo0-indexed page number for pagination.
list_idYesThe list id.
reverseNoReverse the sort order (serialized true/false).
archivedNoInclude archived items — serialized as archived=true/false. Default false.
order_byNoSort field, e.g. 'created', 'updated', 'due_date', 'id'.
statusesNoFilter by status names (repeated statuses[] params), e.g. ["open","in progress"].
subtasksNoInclude subtasks (serialized true/false).
assigneesNoFilter by assignee user ids (repeated assignees[] params).
due_date_gtNoOnly tasks due after this Unix time in ms.
due_date_ltNoOnly tasks due before this Unix time in ms.
include_closedNoInclude closed tasks (serialized true/false).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotation readOnlyHint=true is consistent with the 'Get' verb. The description adds that filters and pagination are supported, but this is already evident from the schema. It doesn't disclose additional behavioral aspects such as response structure or default pagination limits, though the annotation reduces the burden.

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?

The description is concise: one sentence for purpose and one for the REST endpoint. Every sentence carries intent, though the REST reference is extra and not strictly necessary for an agent. No redundant content.

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

Completeness3/5

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

For a read-only list operation with a rich schema, the description covers the core functionality. However, it doesn't mention the return format or how this differs from searching tasks, and the lack of an output schema leaves some ambiguity. Given the tool's complexity, slightly more guidance would improve completeness.

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?

All 11 parameters have detailed descriptions in the schema (100% coverage). The description only summarizes 'optional filters and pagination' without adding new parameter-level semantics, so it doesn't provide value beyond what the schema already offers.

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 tool retrieves tasks within a specific list, using the verb 'Get' and specifying the resource. It distinguishes from sibling tools like clickup_get_task (singular) and clickup_search_tasks by anchoring to a list context, though it doesn't explicitly name those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes 'with optional filters and pagination,' indicating parameters and pagination usage. However, it provides no explicit guidance on when to prefer this tool over clickup_search_tasks or other siblings, nor does it mention exclusions when to avoid using it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All clickup toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool targets a unique resource+action combination, with clear scoping (e.g., get_tasks vs search_tasks differ by list vs workspace, list_lists vs list_folderless_lists by parent). No two tools appear to do the same thing, and the descriptions make boundaries explicit.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern (create_, get_, list_, search_, update_+resource), prefixed with clickup_. No camelCase or unconventional verbs are present.

Tool Count5/5

14 tools is a well-scoped size for a project management API, covering hierarchy traversal (workspaces, spaces, folders, lists), task operations, comments, and user info. Each tool serves a clear purpose without unnecessary bloat.

Completeness4/5

The surface covers core CRUD for tasks (create, read, update) and comments, plus full hierarchy listing and search. Minor gaps include no delete task/comment and no update/list operations for folders/lists, but these are workable and don't hinder the primary workflows.

Resources