Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_invite_user_to_workspace

Invite a full member to a ClickUp Workspace by email, granting standard or admin access across the workspace. Use for internal teammates who need broad visibility.

Instructions

Invite a full member to a Workspace by email.

Members are heavier-weight than guests: once added, they can see every Space/Folder/List they have permission to per the Workspace's sharing settings, rather than only items explicitly shared with them. Note: Enterprise plan only — returns 403 on other plans.

When to Use:

  • Onboarding an internal teammate who should have standard (or admin) access across the Workspace.

When NOT to Use:

  • Onboarding an external collaborator who should only see specific items — use clickup_invite_guest_to_workspace instead.

Returns: A confirmation string with the invited member's email and admin flag, or an Error ... string on failure.

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

Error Handling: 403 means the Workspace is not on the Enterprise plan (or you lack admin rights). 400 usually means the email is malformed or already a member.

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 adds valuable behavioral context beyond annotations: that members see items based on workspace sharing settings, that the tool is Enterprise-only with 403 error, and includes error handling for common failure modes. No contradiction with annotations found.

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, no fluff, and includes practical examples and error handling. Every sentence serves a purpose, and it is front-loaded with the core action.

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 relatively simple invite tool, the description covers all necessary aspects: core functionality, when to use vs. alternatives, return value, error scenarios, and an example. Nothing essential is missing.

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 input schema already provides descriptions for all parameters, so the description adds marginal value beyond an example usage. While schema coverage is technically 0% per context signals, the schema itself is well-described, warranting a baseline score of 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?

The description clearly states it invites a full member to a workspace by email, distinguishes between members and guests, and contrasts with the sibling tool clickup_invite_guest_to_workspace, making the purpose unmistakable.

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 when to choose this tool over the guest invite alternative, and also mention the Enterprise plan requirement, leaving no ambiguity.

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