Skip to main content
Glama
MikelA92

Metabase MCP Server

by MikelA92

list_dashboards

Retrieve all available dashboards from Metabase to discover or locate specific dashboards by name. This read-only operation provides access to dashboard information.

Instructions

📊 [SAFE] List all dashboards in Metabase. Use this to discover available dashboards or find dashboards by name. Risk: None - read-only operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the list_dashboards tool. It fetches all dashboards from the Metabase API endpoint '/api/dashboard' and returns a formatted text response listing up to 50 dashboards with their IDs and names.
      async listDashboards() {
        this.logger.debug('Listing dashboards');
        const dashboards = await this.apiClient.makeRequest('/api/dashboard');
        
        return {
          content: [
            {
              type: 'text',
              text: `Found ${dashboards.length} dashboards:
    ${dashboards.slice(0, 50).map(d => 
      `- ID: ${d.id} | Name: ${d.name}`
    ).join('\n')}${dashboards.length > 50 ? `\n... and ${dashboards.length - 50} more dashboards` : ''}`,
            },
          ],
        };
      }
  • The schema definition for the list_dashboards tool, specifying its name, description, and empty input schema (no parameters required). This is part of the TOOL_DEFINITIONS array used for tool discovery.
    {
      name: 'list_dashboards',
      description: '📊 [SAFE] List all dashboards in Metabase. Use this to discover available dashboards or find dashboards by name. Risk: None - read-only operation.',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • The registration/dispatch point in the executeTool switch statement that maps the 'list_dashboards' tool name to the dashboardHandlers.listDashboards() method.
    case 'list_dashboards':
      return await this.dashboardHandlers.listDashboards();
  • Instantiation of the DashboardHandlers class, which contains the listDashboards method, making it available for tool execution.
    this.dashboardHandlers = new DashboardHandlers(this.apiClient);
  • Import of the DashboardHandlers class containing the tool handler.
    import { DashboardHandlers } from './handlers/dashboardHandlers.js';
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 safety ('[SAFE]', 'read-only operation') and risk ('Risk: None'), though it lacks details on pagination, sorting, or response format.

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?

It is front-loaded with key info (emoji, safety, purpose) in a single, efficient sentence with zero waste, making it easy to parse quickly.

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?

For a simple read-only tool with no parameters and no output schema, the description covers safety and purpose adequately but could benefit from mentioning return format or limitations, given the lack of annotations and output schema.

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% coverage, so no parameter details are needed. The description appropriately does not add param info, earning a baseline 4 for matching the schema's simplicity.

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 verb ('List') and resource ('all dashboards in Metabase'), and distinguishes it from siblings by specifying it's for discovery or finding by name, unlike get_dashboard which likely retrieves a specific dashboard.

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?

It provides clear context on when to use ('to discover available dashboards or find dashboards by name'), but does not explicitly mention when not to use or name alternatives like get_dashboard, which could be inferred but not stated.

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