Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_add_guest_to_task

Grant an existing guest access to a specific task with chosen permission level (read, comment, edit, create). For Enterprise workspaces only.

Instructions

Share a single task with an existing guest at a given permission level.

The guest must already exist on the Workspace (see clickup_invite_guest_to_workspace). Note: Enterprise plan only — returns 403 on other plans.

When to Use:

  • Giving a guest visibility into exactly one task without exposing the rest of the list/folder/space.

When NOT to Use:

  • Sharing an entire list or folder — use clickup_add_guest_to_list / clickup_add_guest_to_folder instead.

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

Examples: params = {"task_id": "abc123", "guest_id": "456", "permission_level": "edit"} params = {"task_id": "CUSTOM-1", "guest_id": "456", "permission_level": "read", "custom_task_ids": True, "team_id": "123"}

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

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 provide readOnlyHint=false, destructiveHint=false, but the description adds valuable context: returns a confirmation string or error string, explains error handling for 403 and 404, and notes that it is a mutation but not destructive. This goes beyond the bare 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?

The description is well-organized with clear sections (purpose, prerequisites, when to use/not use, returns, examples, error handling). It is concise yet comprehensive, with no wasted words.

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 (permission levels, guest prerequisite, plan restriction, error handling), the description covers all essential aspects: purpose, prerequisites, usage conditions, return value, error handling, and examples. It references sibling tools and includes sufficient detail for correct invocation.

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 description coverage is 0%, but the description adds value through examples showing usage of custom_task_ids and team_id, and clarifies permission_level enum values ('read (view), comment, edit, or create (full access)'). This compensates for the lack of coverage.

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 'Share a single task with an existing guest at a given permission level.' It specifies the action (share), resource (task), and recipient (existing guest), and distinguishes itself from sibling tools like clickup_add_guest_to_list and clickup_add_guest_to_folder by emphasizing a single task.

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 includes explicit 'When to Use' and 'When NOT to Use' sections, directs to alternative tools for list/folder sharing, and states prerequisites (guest must exist via clickup_invite_guest_to_workspace) and plan restrictions (Enterprise only).

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