clickup_list_foldersList folders in a space. ClickUp REST: GET /space/{space_id}/folder.
| Name | Required | Description | Default |
|---|---|---|---|
| archived | No | Include archived items — serialized as archived=true/false. Default false. | |
| space_id | Yes | The space 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 already signals a safe read operation, and the description adds the REST endpoint as an implementation detail. However, it does not disclose response behavior, pagination, or the effect of the archived parameter (though archived is documented in the schema). Overall, it adds minimal extra context beyond the annotation, so a 3 is appropriate.
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 two short sentences, immediately stating the purpose and the REST endpoint. It is front-loaded, free of fluff, and every sentence contributes useful information, making it highly concise and well-structured.
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 list tool with robust schema annotations and no output schema, the description is adequate. It clearly states the action and resource, and the REST endpoint adds useful context. However, it lacks guidance on when to use it versus sibling tools and provides no info about return values, which is a minor gap. Overall, it is sufficiently complete for its simplicity.
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 description coverage is 100%, with both space_id and archived fully documented in the input schema. The description only repeats the 'space' context from the REST path, adding little beyond what the schema already provides. Thus, it meets the baseline of 3 without adding informative parameter details.
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 'List folders in a space' clearly identifies the action (list) and the resource (folders within a space), with the REST endpoint adding precision. It does not explicitly differentiate from sibling tools like clickup_list_lists or clickup_list_folderless_lists, but the phrase 'in a space' provides enough scope to distinguish it from broader listing tools.
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 is provided on when to use this tool versus alternatives. The description does not mention any preconditions, exclusions, or suggest sibling tools for different scenarios, leaving the agent to infer usage solely from the title and siblings.
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.