Skip to main content
Glama
MikelA92

Metabase MCP Server

by MikelA92

list_users

Retrieve all user accounts in Metabase to manage access permissions and audit system usage. Requires administrator privileges.

Instructions

👥 [SAFE - REQUIRES ADMIN] List all Metabase users. Requires admin permissions. Use this to see who has access to Metabase. Risk: None - read-only, but may fail if not admin.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the list_users tool. Fetches all users from Metabase API '/api/user/' and returns a formatted text list with user details (ID, name, email, admin status).
      async listUsers() {
        this.logger.debug('Listing users');
        const users = await this.apiClient.makeRequest('/api/user/');
        
        return {
          content: [
            {
              type: 'text',
              text: `Users (${users.length}):
    ${users.map(u => 
      `- ID: ${u.id} | Name: ${u.common_name} | Email: ${u.email} | Admin: ${u.is_superuser}`
    ).join('\n')}`,
            },
          ],
        };
      }
  • Tool schema definition including name, description, and empty input schema (no parameters required). Used by the MCP server for tool listing and validation.
    {
      name: 'list_users',
      description: '👥 [SAFE - REQUIRES ADMIN] List all Metabase users. Requires admin permissions. Use this to see who has access to Metabase. Risk: None - read-only, but may fail if not admin.',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Registers and dispatches the list_users tool call to the UserHandlers.listUsers() method in the MCP server's executeTool switch statement.
    case 'list_users':
      return await this.userHandlers.listUsers();
Behavior4/5

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

Since no annotations are provided, the description carries full burden and does well by disclosing: permission requirements ('Requires admin permissions'), safety profile ('SAFE - REQUIRES ADMIN', 'Risk: None - read-only'), and failure conditions ('may fail if not admin'). It doesn't mention pagination, sorting, or return format details, keeping it from a perfect score.

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?

Front-loaded with key information (purpose, safety, permissions) in a single, efficient sentence. Every phrase adds value: the emoji reinforces purpose, bracketed tags highlight critical info, and the risk statement clarifies behavior. Zero wasted words.

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 read-only tool with no output schema, the description is nearly complete: covers purpose, usage, permissions, and safety. It lacks details on return format (e.g., list structure, fields included) which would be helpful for an agent, but given the simplicity, this is a minor gap.

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 parameters and 100% schema coverage, the baseline is 4. The description adds no parameter-specific information (as there are none), which is appropriate. It could theoretically score 5 if it explicitly noted 'no parameters needed', but the current text is sufficient.

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 ('List all Metabase users') and resource ('Metabase users'), distinguishing it from sibling tools like get_current_user (single user) or other list_* tools (different resources). The inclusion of '👥' emoji reinforces the user-focused purpose.

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 states when to use ('Use this to see who has access to Metabase') and provides clear prerequisites ('Requires admin permissions'). It also distinguishes from alternatives by specifying this lists ALL users, unlike get_current_user which returns only the current user.

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/MikelA92/metabase-mcp-mab'

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