Skip to main content
Glama
CW-Codewalnut

Metabase MCP Server

delete_metabase_user

Remove user accounts from the Metabase business intelligence platform by specifying the user ID to manage access control and user administration.

Instructions

Delete a user from Metabase.

Args: user_id (int): ID of the user to delete.

Returns: Dict[str, Any]: Deletion confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'delete_metabase_user' tool. It is decorated with @mcp.tool() and accepts a user_id parameter to delete a user from Metabase via the DELETE /api/user/{user_id} endpoint.
    @mcp.tool()
    async def delete_metabase_user(user_id: int) -> Dict[str, Any]:
        """
        Delete a user from Metabase.
    
        Args:
            user_id (int): ID of the user to delete.
    
        Returns:
            Dict[str, Any]: Deletion confirmation.
        """
        logger.info(f"Deleting user {user_id}")
        return await make_metabase_request(RequestMethod.DELETE, f"/api/user/{user_id}")
  • The FastMCP instance initialization that enables tool registration via the @mcp.tool() decorator pattern.
    mcp = FastMCP("metabase", lifespan=app_lifespan)
  • The 'make_metabase_request' helper function that handles HTTP requests to the Metabase API. It manages the session, request construction, error handling, and response parsing for all API calls including the delete_metabase_user tool.
    async def make_metabase_request(
        method: RequestMethod,
        endpoint: str,
        data: Optional[Dict[str, Any] | bytes] = None,
        params: Optional[Dict[str, Any]] = None,
        json: Any = None,
        headers: Optional[Dict[str, str]] = None,
    ) -> Dict[str, Any]:
        """
        Make a request to the Metabase API.
        
        Args:
            method: HTTP method to use (GET, POST, PUT, DELETE)
            endpoint: API endpoint path
            data: Request data (for form data)
            params: URL parameters
            json: JSON request body
            headers: Additional headers
            
        Returns:
            Dict[str, Any]: Response data
            
        Raises:
            MetabaseConnectionError: When the Metabase server is unreachable
            MetabaseResponseError: When Metabase returns a non-2xx status code
            RuntimeError: For other errors
        """
        
        if not METABASE_URL or not METABASE_API_KEY:
            raise RuntimeError("METABASE_URL or METABASE_API_KEY environment variable is not set. Metabase API requests will fail.")
    
        if session is None:
            raise RuntimeError("HTTP session is not initialized. Ensure app_lifespan was called.")
    
        try:
            request_headers = headers or {}
            
            logger.debug(f"Making {method.name} request to {METABASE_URL}{endpoint}")
            
            # Log request payload for debugging (omit sensitive info)
            if json and logger.level <= logging.DEBUG:
                sanitized_json = {**json}
                if 'password' in sanitized_json:
                    sanitized_json['password'] = '********'
                logger.debug(f"Request payload: {sanitized_json}")
                
            response = await session.request(
                method=method.name,
                url=endpoint,
                timeout=aiohttp.ClientTimeout(total=30),
                headers=request_headers,
                data=data,
                params=params,
                json=json,
            )
    
            try:
                # Handle 500 errors with more detailed info
                if response.status >= 500:
                    error_text = await response.text()
                    logger.error(f"Server error {response.status}: {error_text[:200]}")
                    raise MetabaseResponseError(response.status, f"Server Error: {error_text[:200]}", endpoint)
                
                response.raise_for_status()
                response_data = await response.json()
                
                # Ensure the response is a dictionary for FastMCP compatibility
                return ensure_dict_response(response_data)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a deletion operation, implying it's destructive, but doesn't disclose critical behavioral traits: whether deletion is permanent/reversible, what permissions are required, if there are side effects (e.g., orphaned resources), rate limits, or error conditions. The return value is mentioned but not elaborated beyond type.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded: the first sentence states the core purpose, followed by structured Args and Returns sections. Every sentence earns its place, though the Returns section could be more informative given the output schema exists. No wasted words, but slightly sparse for a destructive operation.

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 this is a destructive tool with no annotations, 0% schema coverage, but an output schema exists, the description is minimally adequate. It covers the basic purpose and parameter, but lacks behavioral context (safety, permissions, side effects) and usage guidance. The output schema mitigates the need to explain return values, but overall completeness is limited for a high-stakes operation.

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?

With 0% schema description coverage and only 1 parameter, the description compensates well by explicitly documenting the parameter in the Args section: 'user_id (int): ID of the user to delete.' This adds essential meaning beyond the bare schema, clarifying the parameter's purpose and type. However, it doesn't specify format constraints (e.g., valid ID range) or examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Delete') and resource ('a user from Metabase'), making the purpose immediately understandable. However, it doesn't differentiate from sibling delete tools (like delete_metabase_card, delete_metabase_collection, etc.) beyond specifying the resource type, which is somewhat implied by the tool name itself.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives. While sibling tools include create_metabase_user and get_metabase_users, the description doesn't mention prerequisites (e.g., user must exist), exclusions (e.g., cannot delete active users), or related operations. The agent must infer usage from context alone.

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/CW-Codewalnut/metabase-mcp-server'

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