Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_workspace_seats

Read-onlyIdempotent

Check used, total, and available member and guest seats for a ClickUp Workspace to determine if you can invite new members or guests without incurring extra charges.

Instructions

Report used, total, and available member and guest seats for a Workspace.

When to Use:

  • Before inviting members/guests, to confirm free seats exist (an invite on a full paid plan may add a billable seat).

When NOT to Use:

  • To read the plan tier — use clickup_get_workspace_plan.

Returns: Member seats (filled/total/empty) and guest seats (filled/total/empty). Guest totals may be reported as "Infinity" on unlimited plans.

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 mark readOnlyHint, idempotentHint, destructiveHint, so safety is clear. Description adds valuable detail: returns 'Infinity' for guest totals on unlimited plans, error handling for 404/401. No contradictions.

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 headings (When to Use, When NOT to Use, Returns, Examples, Error Handling). No fluff, every section adds value. Concise yet comprehensive.

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?

Covers all aspects: purpose, usage context, parameter behavior, return structure, error scenarios, examples. Agent has everything needed to invoke correctly, even without output schema (though one exists).

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?

Schema description coverage is 0% per context, but description compensates by noting default team_id from CLICKUP_TEAM_ID and showing response_format usage in examples. Does not fully describe each parameter's meaning but enough for usage.

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 workspace seats (used/total/available for members and guests). Distinguished from sibling clickup_get_workspace_plan by focusing on seat counts rather than plan tier.

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' (before inviting members/guests) and 'When NOT to Use' (to read plan tier, with alternative clickup_get_workspace_plan). Full guidance on context.

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