Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_lists

Read-onlyIdempotent

Retrieve all lists inside a specific folder. Supports pagination and optional archived view.

Instructions

List the Lists that belong to a Folder.

When to Use:

  • Enumerating every List inside a specific Folder.

When NOT to Use:

  • The Space has no Folders — use clickup_get_folderless_lists.

  • You already have the list_id and need full detail — use clickup_get_list.

Returns: Markdown (default) or JSON per response_format.

Pagination: ClickUp returns every List belonging to the Folder in one response; this tool then windows the result with limit/offset to keep responses small, reporting has_more and the next offset when applicable.

Examples: params = {"folder_id": "12345"} params = {"folder_id": "12345", "archived": True, "limit": 50}

Error Handling: 404 means folder_id does not exist or is not 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 and destructiveHint, so the description's main behavioral additions are the return format options, pagination behavior (windowing, has_more), and error handling for 404. These add useful context beyond annotations. No contradictions found.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with distinct sections (When to Use, When NOT to Use, Returns, Pagination, Examples, Error Handling). Every sentence serves a purpose, though it could be slightly more concise. Front-loading is good.

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?

The description covers all essential aspects: purpose, usage alternatives, pagination behavior, error handling, and return format. Given the presence of an output schema, it does not need to detail return values. The description is complete for the tool's complexity.

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 provides descriptions for all parameters, so the tool description does not need to repeat them. It adds example usage but does not elaborate on parameter semantics beyond the schema. Baseline 3 is appropriate given schema coverage.

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 Lists that belong to a Folder.' It also distinguishes itself from sibling tools by specifying when not to use it (use clickup_get_folderless_lists or clickup_get_list instead), making the purpose unambiguous.

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 'When to Use' and 'When NOT to Use' sections, including specific alternative tool names. This gives the agent clear guidance on when to invoke this tool versus others.

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