Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_remove_guest_from_folder

DestructiveIdempotent

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

Instructions

Revoke a guest's access to a Folder.

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

When to Use:

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

When NOT to Use:

  • Removing just one List or task — use clickup_remove_guest_from_list / clickup_remove_guest_from_task.

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

Examples: params = {"folder_id": "321", "guest_id": "456"}

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate destructiveHint=true, but the description adds specifics: returns a confirmation string or error, and details on error codes (403 for plan, 404 for missing IDs). This goes beyond the 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?

The description is well-structured with clear sections: purpose, plan note, when to use, when not to use, returns, example, and error handling. It is concise and every sentence adds value.

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 presence of an output schema (as indicated by context signals), the description covers returns, error handling, plan restriction, and provides an example. It is fully complete for a destructive removal tool.

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 has descriptions for all three parameters (guest_id, folder_id, include_shared), so schema_description_coverage is 100%. The description does not mention include_shared, but since the schema is sufficient, baseline 3 is appropriate.

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 starts with a clear verb+resource: 'Revoke a guest's access to a Folder.' It distinguishes from siblings like clickup_remove_guest_from_list and clickup_remove_guest_from_task by specifying when not to use them.

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 provides 'When to Use' and 'When NOT to Use' sections with alternative tool names, making it easy for the agent to choose the correct tool.

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