Skip to main content
Glama

get_workspace_seats

Retrieve details about user licenses in a ClickUp workspace, including seat allocation and availability.

Instructions

Get information about seats (user licenses) in a ClickUp workspace. Returns details about seat allocation and availability.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspace_idYesThe ID of the workspace to get seats information for

Implementation Reference

  • The MCP tool handler for 'get_workspace_seats'. It registers the tool with a Zod schema for workspace_id, calls authClient.getWorkspaceSeats(), and returns the result as JSON.
    // Workspace and Auth tools
    server.tool(
      'get_workspace_seats',
      'Get information about seats (user licenses) in a ClickUp workspace. Returns details about seat allocation and availability.',
      { workspace_id: z.string().describe('The ID of the workspace to get seats information for') },
      async ({ workspace_id }) => {
        try {
          const result = await authClient.getWorkspaceSeats(workspace_id);
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error getting workspace seats:', error);
          return {
            content: [{ type: 'text', text: `Error getting workspace seats: ${error.message}` }],
            isError: true
          };
        }
      }
  • Input schema for the 'get_workspace_seats' tool: workspace_id (string).
    { workspace_id: z.string().describe('The ID of the workspace to get seats information for') },
  • The AuthClient.getWorkspaceSeats() method that calls the ClickUp API endpoint /team/{workspaceId}/seats to retrieve seat information.
    async getWorkspaceSeats(workspaceId: string): Promise<{
      members: object;
      filled_members_seats: number;
      total_member_seats: number;
      empty_member_seats: number;
      guests: object;
      filled_guest_seats: number;
      total_guest_seats: number;
      empty_guest_seats: number;
    }> {
      try {
        return await this.client.get(`/team/${workspaceId}/seats`);
      } catch (error) {
        console.error('Error getting workspace seats:', error);
        throw error;
      }
    }
  • The tool is registered via server.tool() inside setupTaskTools(), which is called from src/index.ts setupTools().
    export function setupTaskTools(server: McpServer): void {
      // Workspace and Auth tools
      server.tool(
        'get_workspace_seats',
        'Get information about seats (user licenses) in a ClickUp workspace. Returns details about seat allocation and availability.',
        { workspace_id: z.string().describe('The ID of the workspace to get seats information for') },
        async ({ workspace_id }) => {
          try {
            const result = await authClient.getWorkspaceSeats(workspace_id);
            return {
              content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
            };
          } catch (error: any) {
            console.error('Error getting workspace seats:', error);
            return {
              content: [{ type: 'text', text: `Error getting workspace seats: ${error.message}` }],
              isError: true
            };
          }
        }
      );
Behavior2/5

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

No annotations provided, so description carries full burden. It only indicates a read operation without disclosing permissions, error handling, or side effects.

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?

Two succinct sentences with zero redundancy, directly stating purpose and return content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple read tool, but lacks details on the structure of returned seat information and does not specify what 'allocation and availability' entails.

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 description already covers the single parameter (workspace_id) with 100% coverage. Description adds no additional semantic value beyond 'workspace ID'.

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 the tool retrieves seat (license) information for a ClickUp workspace, distinguishing it from sibling tools that focus on tasks, lists, folders, and docs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description implies usage for retrieving seat details but does not explicitly state when to use this tool versus alternatives like get_workspaces, which lacks seat info.

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/nsxdavid/clickup-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server