Skip to main content
Glama
DiversioTeam

ClickUp MCP Server

by DiversioTeam

get_current_user

Retrieve details of the currently authenticated ClickUp user to verify identity and access permissions for task management operations.

Instructions

Get details of the currently authenticated user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main tool handler function that fetches and formats the current user data using the ClickUpClient.
    async def get_current_user(self) -> Dict[str, Any]:
        """Get details of the currently authenticated user."""
        user = await self.client.get_current_user()
    
        return {
            "id": user.get("id"),
            "username": user.get("username"),
            "email": user.get("email"),
            "initials": user.get("initials"),
            "color": user.get("color"),
            "profilePicture": user.get("profilePicture"),
            "role": user.get("role"),
        }
  • Input schema definition for the get_current_user tool, which requires no parameters.
    Tool(
        name="get_current_user",
        description="Get details of the currently authenticated user",
        inputSchema={
            "type": "object",
            "properties": {},
        },
    ),
  • Registers the get_current_user method as a tool handler in the internal tools dictionary.
    "get_task_analytics": self.get_task_analytics,
    # User management
    "list_users": self.list_users,
    "get_current_user": self.get_current_user,
    "find_user_by_name": self.find_user_by_name,
  • Helper method on ClickUpClient that makes the API request to retrieve the current user data.
    async def get_current_user(self) -> Dict[str, Any]:
        """Get the current authenticated user."""
        data = await self._request("GET", "/user")
        return data.get("user", {})
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates a read operation ('Get details'), which implies non-destructive behavior, but does not specify authentication requirements, rate limits, or return format details. The description adds basic context but lacks depth on behavioral traits.

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 a single, efficient sentence that front-loads the core purpose without unnecessary words. Every part of the sentence earns its place by specifying the action, resource, and context, making it highly concise and well-structured.

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?

Given the tool's simplicity (0 parameters, no output schema), the description is adequate but minimal. It covers the basic purpose and context but lacks details on authentication needs, return values, or error handling. For a tool with no annotations or output schema, more completeness would enhance usability.

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 has 0 parameters with 100% description coverage, so the schema fully documents the lack of inputs. The description does not add parameter information beyond this, which is acceptable as there are no parameters to explain. A baseline of 4 is appropriate for zero-parameter tools.

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 the specific action ('Get details') and resource ('currently authenticated user'), distinguishing it from sibling tools like 'find_user_by_name' or 'list_users' which operate on different user scopes. It precisely communicates that this tool retrieves information about the user associated with the current authentication context.

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

Usage Guidelines4/5

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

The description implies usage context by specifying 'currently authenticated user,' suggesting this tool should be used when needing details about the authenticated user rather than other users. However, it does not explicitly state when not to use it or name alternatives like 'list_users' or 'find_user_by_name,' which could provide more comprehensive guidance.

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

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