Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_folder_templates

Read-onlyIdempotent

List folder templates in a ClickUp workspace, returning their IDs for use in creating folders from templates.

Instructions

List the Folder templates available in a Workspace.

Calls GET /team/{team_id}/folder_template. Template ids are t--prefixed and feed directly into clickup_create_folder_from_template.

When to Use:

  • To discover which Folder template id to pass to clickup_create_folder_from_template.

When NOT to Use:

  • To list actual Folders in a Space — use clickup_get_folders.

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

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

Examples: params = {"team_id": "90130912", "limit": 20, "offset": 0}

Error Handling: 404 means team_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 readOnly and idempotent hints. Description adds that the tool returns a markdown/JSON list or error string, explains client-side pagination with limit/offset, and covers error handling for 404. No contradictions.

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?

Very concise and well-structured with clear sections for purpose, usage, returns, pagination, examples, and error handling. Every sentence adds value without 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 that an output schema exists, the description adequately covers the return type and possible error. Pagination and error handling are explained, making it complete for a list 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?

Input schema has detailed descriptions for all parameters (limit, offset, team_id, response_format) covering their meaning and default values. The description adds no significant extra meaning beyond what the schema already provides, so baseline at 3.

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?

Clearly states 'List the Folder templates available in a Workspace' with specific verb and resource. Distinguishes from sibling tool clickup_get_folders by explicitly stating when not to use. Also links to clickup_create_folder_from_template.

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 on appropriate context and alternatives, including naming the sibling tool clickup_get_folders for actual folder listing.

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