clickup_list_listsList the lists inside a folder. ClickUp REST: GET /folder/{folder_id}/list.
| Name | Required | Description | Default |
|---|---|---|---|
| archived | No | Include archived items — serialized as archived=true/false. Default false. | |
| folder_id | Yes | The folder id. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation declares the tool safe for reads, and the description adds the REST GET endpoint as confirmation. But no additional behavioral details are provided, such as pagination or return format, which is acceptable given the 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that includes the REST endpoint, making it concise and waste-free. Every word serves a purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only list tool, the description together with the schema and annotations is complete. It states the core operation, the required resource, and the read-only nature, with no missing essential information.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema describes both parameters (folder_id and archived), covering 100% of the schema. The description does not add further meaning, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource ('List the lists inside a folder'), clearly distinguishing it from sibling tools like list_folderless_lists and list_folders. The REST endpoint 'GET /folder/{folder_id}/list' adds precision.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The context is clear: this tool is specifically for lists within a given folder, as implied by the required 'folder_id' parameter. However, it does not explicitly mention alternatives or exclusions, though the sibling tool names make the intended use evident.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.