Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_remove_user_from_workspace

DestructiveIdempotent

Deactivate a full member's access to a workspace. Use for offboarding internal teammates who need to have their workspace access removed.

Instructions

Deactivate a full member's access to a Workspace.

Note: Enterprise plan only — returns 403 on other plans.

When to Use:

  • Offboarding an internal teammate who should lose all Workspace access.

When NOT to Use:

  • Revoking a guest's access — use clickup_remove_guest_from_workspace instead.

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

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

Error Handling: 403 means the Workspace is not on the Enterprise plan (or you lack admin rights). 404 means the user 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?

Description adds behavioral context beyond annotations by detailing return type (confirmation or error string), and error handling for 403 and 404. No contradiction with 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?

Description is well-structured with clear sections, front-loaded purpose, and no unnecessary words. Every sentence serves a purpose.

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 simplicity and the presence of annotations and output schema, the description covers all necessary aspects: purpose, usage, error handling, and restrictions. It is fully informative for an AI agent.

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?

Input schema already provides descriptions for each parameter (team_id, user_id). The description adds an example of usage, which clarifies parameter formatting but does not add new semantic meaning.

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 deactivates a full member's access to a Workspace, using a specific verb and resource. It distinguishes itself from the sibling tool for removing guests.

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, specifying an alternative tool for guests. Also notes the Enterprise plan requirement, providing clear decision criteria for the agent.

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