Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_remove_guest_from_workspace

DestructiveIdempotent

Remove a guest from an entire ClickUp Workspace, revoking access to all tasks, lists, and folders they were shared on. Only works on Enterprise plans.

Instructions

Revoke a guest's access to an entire Workspace.

This removes the guest from every task/list/folder they were shared on — it is not scoped to a single item. Note: Enterprise plan only — returns 403 on other plans.

When to Use:

  • Offboarding an external collaborator entirely.

When NOT to Use:

  • Revoking access to just one task/list/folder — use clickup_remove_guest_from_task / _list / _folder instead.

Returns: A confirmation string, or an Error ... string on failure.

Examples: params = {"team_id": "123", "guest_id": "456"}

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

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 plan restriction (Enterprise only, 403 on other plans), describes the scope of removal (every task/list/folder), and explains error handling (403, 404). This adds significant context beyond annotations which indicate destructive and idempotent hints.

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 a clear summary, usage guidelines, examples, and error handling. Front-loaded with main action. No unnecessary content.

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?

Covers the essential aspects: what it does, when to use, plan restrictions, expected output, and error codes. Output schema is mentioned indirectly via return description. Complete for this tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% (tool description does not describe parameters), so the description must compensate. However, it only provides an example usage without adding meaning beyond what the input schema already provides (workspace ID and guest ID descriptions are in schema). The example does not clarify sources or formats for the IDs.

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: 'Revoke a guest's access to an entire Workspace.' It uses a specific verb and resource, and distinguishes from siblings by noting it is not scoped to a single item, with explicit alternatives provided.

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 ('Offboarding an external collaborator entirely') and when NOT to use, with direct references to alternative tools (clickup_remove_guest_from_task/_list/_folder).

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