Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_tasks

Read-onlyIdempotent

Retrieve tasks from one ClickUp List using filters like status, assignee, tags, and due date, with sorting and pagination.

Instructions

List tasks inside ONE List, with filters and sorting.

Calls GET /list/{list_id}/task. Scope is a single List. Filter by statuses, assignees, tags, custom task types, and date ranges (created/updated/due/done, all unix ms), and sort with order_by + reverse.

When to Use:

  • You know the List and want its tasks (a sprint board, a backlog column).

When NOT to Use:

  • You need tasks across several Lists/Folders/Spaces at once, or you do not know which List they live in — use clickup_get_filtered_team_tasks, which searches the whole Workspace.

  • You already have a task id — use clickup_get_task.

Returns: A paginated markdown summary (one bullet per task) or JSON. Only the first 50 tasks of a page are rendered to stay under the size limit.

Pagination: Page-based: pass page (0-indexed, up to 100 tasks per page). When the tool reports "More available", request the next page number.

Examples:

  • params = {"list_id": "901", "statuses": ["in progress"], "order_by": "due_date"}

  • Next page: params = {"list_id": "901", "page": 1}

Error Handling: 404 means the List id is wrong; an empty result is a valid page past the end.

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?

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds valuable operational details: pagination mechanics (page-based, up to 100 tasks per page, 'More available' signal), return format constraints (first 50 tasks rendered), and error handling (404 for wrong list id, empty result past end). 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?

The description is well-organized: a one-line summary, followed by clear sections for when to use/not use, returns, pagination, examples, and error handling. Every sentence serves a purpose, and key information is front-loaded.

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 the tool's complexity (many parameters, pagination, error cases), the description covers all essential aspects: scope, filtering, sorting, pagination mechanics, return format, and error handling. The presence of an output schema means return structure is covered elsewhere, so the description is appropriately complete.

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?

The input schema provides descriptions for all parameters (100% coverage), so the description's role is to add value beyond that. It summarizes the filter surface (statuses, assignees, tags, etc.) and provides usage examples, which helps an agent quickly grasp the parameter landscape. However, the schema already documents each parameter, so the description adds moderate extra value.

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 'List tasks inside ONE List, with filters and sorting,' specifying the verb (list) and resource (tasks within a single list). It explicitly distinguishes from sibling tools by naming alternatives and their appropriate contexts.

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?

The description includes dedicated 'When to Use' and 'When NOT to Use' sections with explicit references to alternative tools (clickup_get_filtered_team_tasks, clickup_get_task), providing clear decision guidance.

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