Skip to main content
Glama

gitlab_get_my_profile

Retrieve your complete GitLab profile including personal information, account settings, security status, and private statistics for dashboard display or data verification.

Instructions

Get the current authenticated user's complete profile

Retrieve your own comprehensive profile information including private settings and detailed statistics not available via public user APIs.

Returns complete profile including:

  • Personal info: email, name, bio, location

  • Account settings: notifications, preferences

  • Statistics: private/public project counts

  • Security: 2FA status, SSH keys count

  • Activity: recent contributions, sign-in history

Use cases:

  • Display user dashboard information

  • Verify account settings and security

  • Show personalized statistics

  • Export profile data

No parameters required - uses authentication token.

Example usage:

{}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'gitlab_get_my_profile' tool. It simply delegates to the GitLabClient's get_my_profile() method to fetch the authenticated user's complete profile information.
    def handle_get_my_profile(client: GitLabClient, arguments: Optional[Dict[str, Any]]) -> Dict[str, Any]:
        """Handle getting current user's complete profile"""
        return client.get_my_profile()
  • The tool schema definition including name, description reference, and empty input schema (no parameters required). This defines the tool's interface for MCP.
    types.Tool(
        name=TOOL_GET_MY_PROFILE,
        description=desc.DESC_GET_MY_PROFILE,
        inputSchema={
            "type": "object",
            "properties": {}
        }
    ),
  • The tool registration in the server's list_tools() handler, which returns the MCP Tool object for 'gitlab_get_my_profile'.
    types.Tool(
        name=TOOL_GET_MY_PROFILE,
        description=desc.DESC_GET_MY_PROFILE,
        inputSchema={
            "type": "object",
            "properties": {}
        }
  • Mapping of tool name to handler function in the TOOL_HANDLERS dictionary, used by server.call_tool() for dispatch.
    TOOL_GET_MY_PROFILE: handle_get_my_profile,
  • Constant definition for the tool name string, used consistently across files.
    TOOL_GET_MY_PROFILE = "gitlab_get_my_profile"
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing authentication requirements ('uses authentication token'), privacy aspects ('private settings', 'not available via public APIs'), and the comprehensive nature of returned data. It doesn't mention rate limits or error conditions, but covers key 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?

Perfectly structured with clear sections: purpose statement, detailed return data breakdown, use cases, and parameter clarification. Every sentence adds value with zero waste, and the information is front-loaded appropriately.

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

Completeness4/5

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

For a 0-parameter tool with no output schema, the description provides excellent context about what data is returned, use cases, and authentication. It could potentially mention response format or error handling, but given the tool's simplicity, it's quite complete.

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 schema has 0 parameters with 100% coverage, so baseline would be 3. The description adds value by explicitly stating 'No parameters required - uses authentication token', which clarifies the authentication mechanism beyond what the empty schema indicates.

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 verb ('Get', 'Retrieve') and resource ('current authenticated user's complete profile') with specific scope. It distinguishes from siblings like 'gitlab_get_user' by emphasizing it's for the authenticated user's own profile with private data not available via public APIs.

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 'Use cases' section provides clear context for when to use this tool (dashboard display, account verification, statistics, data export). However, it doesn't explicitly state when NOT to use it or mention alternatives like 'gitlab_get_user' for other users' public profiles.

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/Vijay-Duke/mcp-gitlab'

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