Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_remove_guest_from_task

DestructiveIdempotent

Remove a guest from a specific task while leaving their access to other shared items intact. Ideal for revoking task-level permissions without removing the guest from the workspace.

Instructions

Revoke a guest's access to a single task.

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

When to Use:

  • Un-sharing one task from a guest while leaving their other shared items intact.

When NOT to Use:

  • Removing the guest from the whole Workspace — use clickup_remove_guest_from_workspace.

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

Examples: params = {"task_id": "abc123", "guest_id": "456"}

Error Handling: 403 means the Workspace is not on the Enterprise plan. 404 means the task 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 declare destructiveHint=true and idempotentHint=true. Description adds critical context: Enterprise plan restriction (403), error codes (403, 404), and return type (confirmation/error string). 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?

Well-structured with bullet sections, front-loaded main action, and includes examples and error handling. Every sentence adds value with no redundancy.

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 annotations and schema, the description covers purpose, usage boundaries, return value, error handling, and plan limitation. Complete for a mutation 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?

Input schema has full description coverage for all 5 parameters, so baseline is 3. The tool description does not add additional parameter meaning beyond what schema already provides.

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?

Description clearly states 'Revoke a guest's access to a single task' with specific verb and resource. It distinguishes from sibling tools like clickup_remove_guest_from_workspace and clickup_add_guest_to_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?

Explicitly provides 'When to Use' and 'When NOT to Use' sections, including a concrete alternative (clickup_remove_guest_from_workspace) for the wrong case.

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