Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_guest

Read-onlyIdempotent

Look up a guest's permission flags and shared tasks, lists, and folders to audit their access before editing or removing them.

Instructions

Look up a guest's permission flags and what has been shared with them.

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

When to Use:

  • Auditing what a guest can currently see/do before editing or removing them.

When NOT to Use:

  • Looking up full Workspace members — use clickup_get_user instead.

Returns: Markdown summary (id, username, email, permission flags, and a count of shared tasks/lists/folders) or the raw JSON payload when response_format="json".

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable context: Enterprise plan only (403 on other plans), return format options (markdown or json), 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?

The description is well-structured with clear sections: purpose, note, when to use/not use, return format, example, error handling. It is concise yet comprehensive, with no redundant information.

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?

The description covers purpose, usage guidelines, return format, example, and error handling. Given the annotations and output schema presence, this is complete. The tool's complexity is low, and all necessary information is provided.

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 input schema already provides descriptions for `team_id`, `guest_id`, and `response_format`. The description adds example usage (`params = {"team_id": "123", "guest_id": "456"}`) and error-handling context that clarifies parameter semantics. The parameter count in context signals (1) is misleading, but the description compensates with clarity.

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 'Look up a guest's permission flags and what has been shared with them.' It specifies the verb (look up) and resource (guest), and distinguishes itself from the sibling tool `clickup_get_user` which is for full Workspace members.

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?

The description explicitly includes 'When to Use' and 'When NOT to Use' sections, naming the alternative tool `clickup_get_user` for workspace members. It also notes the Enterprise plan restriction. This provides clear guidance on when to select this tool over others.

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