Skip to main content
Glama
windalfin

ClickUp MCP Server

by windalfin

get_list

Retrieve details about a specific ClickUp list using either the list ID or list name to access task organization information.

Instructions

Retrieve details about a specific ClickUp list. You MUST provide either listId or listName. Using listId is more reliable as list names might not be unique.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listIdNoID of the list to retrieve. Use this instead of listName if you have the ID.
listNameNoName of the list to retrieve. May be ambiguous if multiple lists have the same name.

Implementation Reference

  • Handler function that resolves the list ID if only name is provided, fetches the list details using listService.getList, and returns formatted JSON response with list info including URL.
    export async function handleGetList(parameters: any) {
      const { listId, listName } = parameters;
      
      let targetListId = listId;
      
      // If no listId provided but listName is, look up the list ID
      if (!targetListId && listName) {
        const listResult = await findListIDByName(workspaceService, listName);
        if (!listResult) {
          throw new Error(`List "${listName}" not found`);
        }
        targetListId = listResult.id;
      }
      
      if (!targetListId) {
        throw new Error("Either listId or listName must be provided");
      }
    
      try {
        // Get the list
        const list = await listService.getList(targetListId);
        
        return {
          content: [{
            type: "text",
            text: JSON.stringify(
              {
                id: list.id,
                name: list.name,
                content: list.content,
                space: {
                  id: list.space.id,
                  name: list.space.name
                },
                status: list.status,
                url: `https://app.clickup.com/${config.clickupTeamId}/v/l/${list.id}`
              },
              null,
              2
            )
          }]
        };
      } catch (error: any) {
        throw new Error(`Failed to retrieve list: ${error.message}`);
      }
    }
  • Tool definition including the name, description, and inputSchema for validating parameters: listId or listName.
    export const getListTool = {
      name: "get_list",
      description: "Retrieve details about a specific ClickUp list. You MUST provide either listId or listName. Using listId is more reliable as list names might not be unique.",
      inputSchema: {
        type: "object",
        properties: {
          listId: {
            type: "string",
            description: "ID of the list to retrieve. Use this instead of listName if you have the ID."
          },
          listName: {
            type: "string",
            description: "Name of the list to retrieve. May be ambiguous if multiple lists have the same name."
          }
        },
        required: []
      }
    };
  • src/server.ts:67-93 (registration)
    Registration of the get_list tool (as getListTool) in the list of available tools returned by the ListToolsRequest handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          workspaceHierarchyTool,
          createTaskTool,
          getTaskTool,
          getTasksTool,
          updateTaskTool,
          moveTaskTool,
          duplicateTaskTool,
          deleteTaskTool,
          createBulkTasksTool,
          updateBulkTasksTool,
          moveBulkTasksTool,
          deleteBulkTasksTool,
          createListTool,
          createListInFolderTool,
          getListTool,
          updateListTool,
          deleteListTool,
          createFolderTool,
          getFolderTool,
          updateFolderTool,
          deleteFolderTool
        ]
      };
    });
  • src/server.ts:128-129 (registration)
    Switch case in CallToolRequest handler that routes 'get_list' calls to the handleGetList function.
    case "get_list":
      return handleGetList(params);
  • Helper function to resolve a list name to its ID by searching the workspace hierarchy, used when only listName is provided.
    export async function findListIDByName(workspaceService: any, listName: string): Promise<{ id: string; name: string } | null> {
      // Use workspace service to find the list in the hierarchy
      const hierarchy = await workspaceService.getWorkspaceHierarchy();
      const listInfo = workspaceService.findIDByNameInHierarchy(hierarchy, listName, 'list');
      if (!listInfo) return null;
      return { id: listInfo.id, name: listName };
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the reliability difference between parameters (listId vs listName), which is useful context. However, it doesn't mention potential errors, rate limits, authentication needs, or return format, leaving gaps for a read operation.

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 two sentences with zero waste: the first states the purpose and mandatory parameter logic, the second provides the key reliability guidance. It's front-loaded and appropriately sized for this 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?

For a simple read tool with 100% schema coverage but no annotations or output schema, the description covers the essential usage logic and parameter guidance. However, it lacks details on error conditions, return format, or how it fits into the broader ClickUp hierarchy, leaving room for improvement.

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 thoroughly. The description adds marginal value by reinforcing the reliability preference (listId over listName) but doesn't provide additional semantic context beyond what's in the schema descriptions.

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 'Retrieve' and the resource 'specific ClickUp list', making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_folder' or 'get_task' beyond the resource type, 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 Guidelines5/5

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

The description provides explicit guidance on when to use parameters ('You MUST provide either listId or listName') and includes a clear alternative preference ('Using listId is more reliable as list names might not be unique'), which directly addresses usage decisions.

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

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