Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_folderless_lists

Read-onlyIdempotent

List all lists that reside directly in a ClickUp space, skipping folder organization. Useful for spaces without folders to enumerate active or archived lists with pagination support.

Instructions

List the Lists that live directly inside a Space (no Folder).

When to Use:

  • Enumerating Lists in a Space that is not organized into Folders.

When NOT to Use:

  • The Space uses Folders — use clickup_get_lists per Folder instead.

  • 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 folderless List in the Space in one response; this tool then windows the result with limit/offset, reporting has_more and the next offset when applicable.

Examples: params = {"space_id": "67890"} params = {"space_id": "67890", "archived": True}

Error Handling: 404 means space_id does not exist or is not accessible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description adds significant behavioral context beyond annotations: explains pagination windowing behavior (has_more, next offset), response format (markdown/json), and error handling (404). Annotations already declare readOnlyHint, idempotentHint, etc., so the description enriches the behavioral model.

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 clear sections (When to Use, When NOT to Use, Returns, Pagination, Examples, Error Handling). It is front-loaded with the core purpose and every sentence adds value. No redundancy.

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 tool's complexity (pagination, format selection, sibling tools, error handling) and the presence of an output schema, the description covers all necessary aspects: usage context, behavioral details, parameter semantics, and troubleshooting. It is fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has descriptions for each parameter, so the baseline is 3. The tool description adds extra context in the 'Pagination' section and examples, clarifying how limit/offset and archived work. It provides more meaning than the schema alone, justifying a 4.

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 starts with a clear verb+resource: 'List the Lists that live directly inside a Space (no Folder).' It explicitly distinguishes from siblings in the 'When NOT to Use' section, naming clickup_get_lists per folder and clickup_get_list as alternatives. This meets the highest standard.

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 clear when-to-use (enumerating folderless lists) and when-not-to-use scenarios (space uses folders, already have list_id), with specific alternative tool names. This is explicit and actionable.

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