get_lists_in_folder
Retrieve all lists within a specified ClickUp folder. Provide the folder ID to get its lists.
Instructions
List all Lists inside a Folder.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| folder_id | Yes | Folder ID. | |
| archived | No |
Retrieve all lists within a specified ClickUp folder. Provide the folder ID to get its lists.
List all Lists inside a Folder.
| Name | Required | Description | Default |
|---|---|---|---|
| folder_id | Yes | Folder ID. | |
| archived | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description only states the basic function. It does not disclose behavior like sorting, pagination, or required permissions, leaving potential pitfalls unaddressed.
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 sentence with no fluff, but could benefit from a brief note on parameters without losing conciseness.
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?
A simple list operation, but missing output schema and parameter explanation makes it incomplete for an agent. The description meets minimal viability but lacks depth.
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?
Schema coverage is 50% (only folder_id described). The description adds no explanation for the archived parameter, leaving its purpose ambiguous despite its boolean type.
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 clearly states it lists all Lists inside a Folder, distinguishing it from related tools like get_list (single list) and get_folderless_lists (lists not in folders).
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?
No guidance on when to use this tool versus alternatives such as get_folderless_lists or get_list. No context or exclusions provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/helbertparanhos/clickup-mcp-pro'
If you have feedback or need assistance with the MCP directory API, please join our Discord server