Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_add_guest_to_list

Add an existing guest to a ClickUp list, granting them read, comment, edit, or create permissions for all tasks in that list.

Instructions

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

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

When to Use:

  • Giving a guest access to a whole List of tasks at once.

When NOT to Use:

  • Sharing just one task — use clickup_add_guest_to_task. Sharing an entire Folder — use clickup_add_guest_to_folder.

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

Examples: params = {"list_id": "789", "guest_id": "456", "permission_level": "comment"}

Error Handling: 403 means the Workspace is not on the Enterprise plan. 404 means the list 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?

Discloses important behavioral aspects beyond annotations: the guest gains visibility into every task, Enterprise plan requirement (403 on other plans), and specific error codes (403, 404). Annotations already indicate mutability (readOnlyHint=false), but description adds significant context.

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?

Well-structured with clear headers (When to Use, When NOT to Use, Returns, Examples, Error Handling). Front-loaded with purpose. Every sentence adds value, no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers essential aspects: purpose, usage guidelines, enterprise limitation, error handling, sibling differentiation, and an example. Missing explicit mention of the include_shared parameter, but output schema exists for response details. Slight gap in not explaining that the guest must already exist.

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 description does not explain all parameters in detail. It provides an example showing list_id, guest_id, and permission_level, but omits the optional include_shared parameter entirely. Schema description coverage is 0%, so description should compensate more. However, the example clarifies usage of the required parameters.

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 the tool shares a List with an existing guest at a given permission level, specifying that the guest gains visibility into every task. It explicitly differentiates from siblings by naming alternatives in the 'When NOT to Use' section.

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?

Provides explicit 'When to Use' and 'When NOT to Use' sections, with clear references to sibling tools (clickup_add_guest_to_task, clickup_add_guest_to_folder) and a note about Enterprise plan restriction.

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