Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_remove_guest_from_list

DestructiveIdempotent

Revoke a guest's access to a List while leaving their other shared items intact. Enterprise plan required.

Instructions

Revoke a guest's access to a List.

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

When to Use:

  • Un-sharing a whole List from a guest while leaving their other shared items intact.

When NOT to Use:

  • Removing just one task — use clickup_remove_guest_from_task.

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

Examples: params = {"list_id": "789", "guest_id": "456"}

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

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 limitation (returns 403 on non-Enterprise) and error codes (403, 404), and describes return type (confirmation string or error string), adding value beyond annotations which only indicate destructiveHint=true.

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: main action, plan note, usage guidance, example, error handling. Each sentence is purposeful and there is no fluff.

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 (3 parameters, output schema present), the description covers purpose, usage constraints, error handling, and return type, making it sufficiently complete for an agent to use correctly.

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?

The description includes an example of parameters, but the input schema already provides descriptions for all parameters. The description does not explain the 'include_shared' parameter, so it adds only marginal value beyond the schema.

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 verb 'Revoke' and resource 'List', and explicitly distinguishes from sibling by stating when NOT to use (for single task removal, use clickup_remove_guest_from_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?

Provides explicit 'When to Use' and 'When NOT to Use' sections, including specific context about un-sharing a whole List while leaving other items intact, and notes the Enterprise plan requirement.

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