Skip to main content
Glama
Sign In
Metabase MCP

Metabase MCP

by 1luvc0d3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

batch_execute

Read-only

Execute up to 20 read operations in a single parallel call. Retrieve dashboards, cards, queries, and schemas without multiple requests.

Instructions

Execute multiple read operations in a single call. Supports up to 20 operations run in parallel. Supported tools: get_dashboard, get_card, execute_card, get_database_schema, execute_query, search_content, list_dashboards, list_databases, list_cards.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operations": "<operations>"
    },
    "name": "batch_execute"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationsYesArray of operations to execute in parallel

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true. The description adds that operations run in parallel and supports up to 20 operations, which are useful behavioral insights. No contradictions.

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?

Two concise sentences that are front-loaded with the primary purpose and key constraints (max 20, parallel). No unnecessary words.

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?

The description is adequate given the rich schema and annotations, but it does not mention the return format or potential error behavior. For a batch tool, explaining response structure would enhance completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage with detailed definitions for each operation's args. The description lists supported tools but adds no deeper semantic meaning beyond what the schema provides.

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 'Execute multiple read operations in a single call', specifying the verb and resource. It also lists all supported tools (get_dashboard, get_card, etc.), which distinguishes it from the individual tool siblings.

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 mentions the limit of 20 operations and parallel execution, but does not explicitly state when to use this tool versus individual calls. However, the implication is clear: use when multiple reads are needed simultaneously.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools