Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_folder

Read-onlyIdempotent

Fetch a specific ClickUp folder with its lists and status workflow. Use to inspect folder details before updating.

Instructions

Fetch one Folder, including its Lists and status workflow.

Calls GET /folder/{folder_id}.

When to Use:

  • To inspect a specific Folder's statuses, Lists, and override_statuses flag before deciding whether to update it.

When NOT to Use:

  • To browse every Folder in a Space — use clickup_get_folders.

Returns: A markdown detail block or JSON object, or an Error ... string.

Examples: params = {"folder_id": "456", "response_format": "markdown"}

Error Handling: 404 means folder_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, destructiveHint. Description adds the HTTP method (GET), return types (markdown/JSON/error), error handling for 404, and the specific API endpoint. This adds behavioral context beyond 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?

Description is well-structured with clear sections: summary, API call, usage guidelines, returns, examples, error handling. Every sentence adds value, no fluff.

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?

For a read-only single-item fetch tool with annotations and output schema, the description covers purpose, when to use, return format, error handling, and example. It is complete and leaves no major gaps.

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?

Schema already has descriptions for both parameters (folder_id: 'The Folder id to fetch', response_format: 'Output format'). The tool description provides an example usage and mentions response format but does not add significant new semantics beyond the schema.

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 'Fetch one Folder, including its Lists and status workflow' which is a specific verb+resource. It also distinguishes from sibling tool 'clickup_get_folders' by the scope (single vs multiple).

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?

Description explicitly provides 'When to Use' (inspect a specific Folder's details before updating) and 'When NOT to Use' (browse all folders, use clickup_get_folders instead), offering clear guidance on selection.

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