Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_add_guest_to_folder

Share a ClickUp Folder with an existing guest by granting read, comment, edit, or create access. The guest gains visibility into all Lists and tasks in that folder.

Instructions

Share a Folder with an existing guest at a given permission level.

The guest gains visibility into every List and task in the Folder. Note: Enterprise plan only — returns 403 on other plans.

When to Use:

  • Giving a guest access to an entire Folder (all its Lists and tasks) at once.

When NOT to Use:

  • Sharing just one List — use clickup_add_guest_to_list. Sharing just one task — use clickup_add_guest_to_task.

Returns: A confirmation string with the folder id, guest id, and permission level, or an Error ... string on failure.

Examples: params = {"folder_id": "321", "guest_id": "456", "permission_level": "create"}

Error Handling: 403 means the Workspace is not on the Enterprise plan. 404 means the folder or guest id does not exist.

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?

Annotations already indicate non-readonly and non-destructive mutation. Description adds that the guest gains visibility into every list and task in the folder, that Enterprise plan is required (403 error), and that confirmation or error string is returned. This goes beyond annotations to clarify exact behavior and constraints.

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 concise, well-structured with clear sections (purpose, when to use/not use, returns, example, errors). Every sentence adds necessary information 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?

For a tool with 4 parameters and an output schema, the description covers purpose, constraints (Enterprise plan), alternatives, error handling, and return format. It is fully adequate for an agent to select and invoke correctly.

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?

Schema has parameter descriptions, but description adds value by clarifying permission_level meanings (e.g., read=view) and providing a usage example. The include_shared parameter is not elaborated, but overall adds nuance beyond 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?

Description clearly states the tool shares a folder with an existing guest at a given permission level. It distinguishes from siblings by specifying folder-level access versus list or task, fulfilling a specific verb+resource purpose.

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?

Explicitly states when to use (giving guest access to entire folder) and when not to use (use list or task alternatives). Also notes Enterprise plan restriction and provides error handling details, giving clear guidance on appropriate usage context.

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