Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_folders

Read-onlyIdempotent

List folders in a ClickUp space using space ID. Supports filtering by archived status and client-side pagination. Returns folder details with task and list counts.

Instructions

List the Folders in a Space.

Calls GET /space/{space_id}/folder. Returns each Folder's task/list counts and its override_statuses flag; use clickup_get_folder for the full status list and nested Lists of one Folder.

When to Use:

  • To discover what Folders exist in a Space before creating or updating one.

  • To check which Folders already override the Space's statuses.

When NOT to Use:

  • To fetch one Folder's full detail — use clickup_get_folder.

  • To list Lists that live directly in the Space (no Folder) — use the folderless-lists tool in tools/lists.py once available.

Returns: A markdown or JSON list of Folders, or an Error ... string.

Pagination: ClickUp returns the full Folder array in one response; this tool slices it client-side via limit/offset for context-window safety.

Examples: params = {"space_id": "90130912", "archived": False, "limit": 20, "offset": 0}

Error Handling: 404 means space_id doesn't exist or isn't accessible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds value by explaining client-side pagination (limit/offset), return content (folder list with counts), and error handling for 404. No contradictions with annotations.

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 well-structured with sections for overview, when to use/not use, returns, pagination, examples, and error handling. Every sentence is informative, no fluff, and front-loaded with the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of output schema and comprehensive annotations, the description provides thorough guidance: usage context, relationship to sibling tools, pagination behavior, example parameters, and error handling. It is fully complete for an agent to understand and 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?

The input schema already contains descriptions for all parameters (space_id, archived, limit, offset, response_format), providing sufficient context. The description does not add additional parameter-level meaning, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'List the Folders in a Space' with the specific API endpoint, and distinguishes from sibling tool `clickup_get_folder` by noting that this tool returns each Folder's task/list counts and `override_statuses` flag.

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?

Explicit 'When to Use' and 'When NOT to Use' sections provide clear guidance: use for discovering folders before creating/updating, or checking status overrides; avoid for full folder details (use `clickup_get_folder`) or for folderless lists (use a yet-unavailable tool).

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

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