Skip to main content
Glama
DiversioTeam

ClickUp MCP Server

by DiversioTeam

list_tasks

Retrieve tasks from ClickUp lists, folders, or spaces with filtering options for status, assignee, and closed tasks.

Instructions

List tasks in a list, folder, or space

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idNoList ID
folder_idNoFolder ID
space_idNoSpace ID
statusesNoFilter by statuses
assigneesNoFilter by assignee IDs
include_closedNoInclude closed tasks

Implementation Reference

  • The core handler function for the
    async def list_tasks(
        self,
        list_id: Optional[str] = None,
        folder_id: Optional[str] = None,
        space_id: Optional[str] = None,
        statuses: Optional[List[str]] = None,
        assignees: Optional[List[int]] = None,
        include_closed: bool = False,
        **kwargs: Any,
    ) -> Dict[str, Any]:
        """List tasks with filters."""
        tasks = await self.client.get_tasks(
            list_id=list_id,
            folder_id=folder_id,
            space_id=space_id,
            statuses=statuses,
            assignees=assignees,
            include_closed=include_closed,
        )
    
        return {
            "tasks": [
                {
                    "id": task.id,
                    "name": task.name,
                    "status": task.status.status,
                    "assignees": [u.username for u in task.assignees],
                    "url": format_task_url(task.id),
                }
                for task in tasks
            ],
            "count": len(tasks),
        }
  • Input schema and description for the list_tasks tool used in MCP tool definitions.
    Tool(
        name="list_tasks",
        description="List tasks in a list, folder, or space",
        inputSchema={
            "type": "object",
            "properties": {
                "list_id": {"type": "string", "description": "List ID"},
                "folder_id": {"type": "string", "description": "Folder ID"},
                "space_id": {"type": "string", "description": "Space ID"},
                "statuses": {
                    "type": "array",
                    "items": {"type": "string"},
                    "description": "Filter by statuses",
                },
                "assignees": {
                    "type": "array",
                    "items": {"type": "integer"},
                    "description": "Filter by assignee IDs",
                },
                "include_closed": {
                    "type": "boolean",
                    "description": "Include closed tasks",
                },
            },
        },
    ),
  • Internal registration of all tools including list_tasks in the ClickUpTools class _tools dictionary, used for dispatching tool calls.
    self._tools: Dict[str, Callable] = {
        "create_task": self.create_task,
        "get_task": self.get_task,
        "update_task": self.update_task,
        "delete_task": self.delete_task,
        "list_tasks": self.list_tasks,
        "search_tasks": self.search_tasks,
        "get_subtasks": self.get_subtasks,
        "get_task_comments": self.get_task_comments,
        "create_task_comment": self.create_task_comment,
        "get_task_status": self.get_task_status,
        "update_task_status": self.update_task_status,
        "get_assignees": self.get_assignees,
        "assign_task": self.assign_task,
        "list_spaces": self.list_spaces,
        "list_folders": self.list_folders,
        "list_lists": self.list_lists,
        "find_list_by_name": self.find_list_by_name,
        # Bulk operations
        "bulk_update_tasks": self.bulk_update_tasks,
        "bulk_move_tasks": self.bulk_move_tasks,
        # Time tracking
        "get_time_tracked": self.get_time_tracked,
        "log_time": self.log_time,
        # Templates
        "create_task_from_template": self.create_task_from_template,
        "create_task_chain": self.create_task_chain,
        # Analytics
        "get_team_workload": self.get_team_workload,
        "get_task_analytics": self.get_task_analytics,
        # User management
        "list_users": self.list_users,
        "get_current_user": self.get_current_user,
        "find_user_by_name": self.find_user_by_name,
    }
  • MCP server handler for listing tools, which returns the tool definitions including list_tasks.
    @self.server.list_tools()
    async def list_tools() -> List[Tool]:
        """List all available tools."""
        return self.tools.get_tool_definitions()
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions listing tasks but doesn't disclose behavioral traits like pagination, rate limits, authentication requirements, or whether it's a read-only operation. The description is minimal and lacks crucial operational context for a tool with 6 parameters.

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 extremely concise - a single sentence with no wasted words. It's front-loaded with the core purpose. However, it may be overly terse given the tool's complexity with 6 parameters and no annotations, potentially sacrificing clarity for brevity.

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?

For a tool with 6 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain return format, pagination, error conditions, or how the multiple container parameters interact. The description should provide more context given the tool's complexity and lack of structured metadata.

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 the schema already documents all 6 parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain relationships between list_id/folder_id/space_id parameters or provide usage examples. Baseline 3 is appropriate when schema does the heavy lifting.

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 verb 'List' and resource 'tasks', specifying the scope as 'in a list, folder, or space'. It distinguishes from siblings like 'search_tasks' by focusing on listing rather than searching, but doesn't explicitly differentiate from other list tools like 'list_folders' or 'list_lists'.

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 explicit guidance on when to use this tool versus alternatives like 'search_tasks' or 'get_task'. The description implies usage for listing tasks within specific containers but doesn't provide context on prerequisites, exclusions, or comparison with sibling tools.

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

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