Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_invite_guest_to_workspace

Invite an external guest to a ClickUp workspace by email. Guests only see tasks and lists explicitly shared with them, ideal for clients or contractors.

Instructions

Invite an external guest to a Workspace by email.

Guests are lighter-weight than full Workspace members: they only see the tasks/lists/folders explicitly shared with them via clickup_add_guest_to_task, clickup_add_guest_to_list, or clickup_add_guest_to_folder. Note: Enterprise plan only — returns 403 on other plans.

When to Use:

  • Onboarding an external collaborator (client, contractor) who should only see specific items rather than the whole Workspace.

When NOT to Use:

  • Adding a full internal team member — use clickup_invite_user_to_workspace instead (users see everything they're a member of by default).

Returns: A confirmation string with the invited guest's id and email, or an Error ... string on failure.

Examples: params = {"team_id": "123", "email": "contractor@example.com", "can_create_views": False}

Error Handling: 403 means the Workspace is not on the Enterprise plan. 400 usually means the email is malformed or already a member/guest.

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?

The description discloses guest limitations (only sees shared items), plan restriction (Enterprise only), and references related functions. Annotations (readOnlyHint=false) are consistent, and description adds value beyond annotations with error handling details.

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 sections (description, when to use, returns, examples, error handling). Concise yet comprehensive, with no unnecessary information.

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 one required parameter and an output schema, the description covers purpose, usage, alternatives, error codes, and includes an example. It is fully adequate for an agent to understand and invoke the tool correctly.

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 description coverage is 0% (context signal), but the description provides an example with one parameter (can_create_views). It does not explain optional parameters or their defaults beyond what's in the schema. The example helps but is insufficient for full parameter understanding.

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 action ('Invite an external guest to a Workspace by email') and distinguishes guests from full members. It also references sibling tools for sharing items, differentiating itself effectively.

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 with specific alternative tool (clickup_invite_user_to_workspace). Also notes Enterprise plan restriction, providing clear usage guidance.

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