Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_workspace_plan

Read-onlyIdempotent

Retrieve the subscription plan of a ClickUp workspace to confirm Enterprise access for audit logs and privacy settings.

Instructions

Report the current subscription plan of a Workspace.

When to Use:

  • To check whether the Workspace is on Enterprise before calling clickup_query_audit_logs / clickup_update_privacy_and_access or other Enterprise-only endpoints.

When NOT to Use:

  • To see seat usage — use clickup_get_workspace_seats.

Returns: The plan name and numeric plan id.

Examples:

  • params = {}

  • params = {"team_id": "9008", "response_format": "json"}

Error Handling: 404 → unknown team id; 401 → bad token. Errors return an Error ... string.

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds return value details (plan name and numeric id) and error handling (404, 401), providing useful context beyond 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 clear sections (When to Use, When NOT to Use, Returns, Examples, Error Handling). Every sentence is informative 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 the simple nature of the tool, the description covers purpose, usage guidelines, return values, examples, and error handling. Adequate for an agent to select and invoke correctly.

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?

Schema already describes both parameters (team_id and response_format) with defaults and description. Description adds examples but no additional param semantics. Baseline score due to schema coverage.

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?

Clearly states it reports the current subscription plan of a Workspace. Distinguishes from sibling clickup_get_workspace_seats by explicitly noting it's not for seat usage.

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. Advises checking Enterprise status before calling Enterprise-only endpoints and names alternative sibling tool for seat usage.

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