Skip to main content
Glama
DiversioTeam

ClickUp MCP Server

by DiversioTeam

list_lists

Retrieve all lists within a ClickUp folder or space to organize and manage project workflows efficiently.

Instructions

List all lists in a folder or space

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idNoFolder ID
space_idNoSpace ID

Implementation Reference

  • The main execution logic for the 'list_lists' tool. Fetches lists from ClickUp API (via client.get_lists) either for a specific folder/space or all spaces, and returns formatted list with IDs, names, space, and folder info.
    async def list_lists(
        self,
        folder_id: Optional[str] = None,
        space_id: Optional[str] = None,
    ) -> Dict[str, Any]:
        """List all lists."""
        if not folder_id and not space_id:
            # List all lists from all spaces
            spaces = await self.client.get_spaces()
            all_lists = []
            for space in spaces:
                lists = await self.client.get_lists(space_id=space.id)
                all_lists.extend(lists)
        else:
            all_lists = await self.client.get_lists(folder_id=folder_id, space_id=space_id)
    
        return {
            "lists": [
                {
                    "id": lst.id,
                    "name": lst.name,
                    "space": lst.space.get("name", "Unknown"),
                    "folder": lst.folder.get("name") if lst.folder else None,
                }
                for lst in all_lists
            ],
            "count": len(all_lists),
        }
  • The input schema definition for the list_lists tool, specifying optional folder_id and space_id parameters.
    Tool(
        name="list_lists",
        description="List all lists in a folder or space",
        inputSchema={
            "type": "object",
            "properties": {
                "folder_id": {"type": "string", "description": "Folder ID"},
                "space_id": {"type": "string", "description": "Space ID"},
            },
        },
    ),
  • MCP server registration: the list_tools handler that exposes the list_lists tool schema to the MCP protocol.
    @self.server.list_tools()
    async def list_tools() -> List[Tool]:
        """List all available tools."""
        return self.tools.get_tool_definitions()
  • Internal registration of the list_lists handler method in the ClickUpTools class _tools dictionary, used by call_tool.
    "list_lists": self.list_lists,
  • Instantiates ClickUpTools (containing list_lists) and MCP Server in ClickUpMCPServer init.
    self.client = ClickUpClient(config)
    self.tools = ClickUpTools(self.client)
    self.server = Server("clickup-mcp")
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the action but doesn't disclose behavioral traits like whether it returns all lists at once or paginates, what permissions are required, or how it handles missing folder/space IDs. This is inadequate for a tool with zero annotation coverage.

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 zero waste. It's front-loaded with the core purpose and appropriately sized for a simple listing tool.

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?

Given the tool's low complexity (simple listing with 2 optional parameters) and no output schema, the description is minimally complete but lacks details on behavior and usage. It covers the basic purpose but doesn't compensate for the absence of annotations or output schema, leaving gaps in understanding how to effectively use the tool.

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 both parameters ('folder_id' and 'space_id'). The description adds minimal value by implying these are optional (since it says 'in a folder or space'), but doesn't provide additional syntax, format details, or usage context beyond what the schema provides.

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 ('all lists'), specifying the scope ('in a folder or space'). It distinguishes from siblings like 'list_folders' and 'list_spaces' by focusing on lists, but doesn't explicitly differentiate from 'find_list_by_name' which also deals with 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 guidance is provided on when to use this tool versus alternatives. It doesn't mention when to use 'list_lists' versus 'find_list_by_name' for searching, or whether it should be used before operations like 'create_task' that might require a list context.

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