Metabase MCP

execute_query

Read-only

Run a SQL SELECT query on a Metabase database and retrieve results with options for field selection, pagination, and response format.

Instructions

Execute a SQL query (SELECT statements only)

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": {
      "database_id": "<database_id>",
      "sql": "<sql>"
    },
    "name": "execute_query"
  }
}

Input Schema

Name	Required	Description
`database_id`	Yes	Database ID to query
`sql`	Yes	SQL query (SELECT statements only)
`fields`	No	Column names to include in results (default: all)
`format`	No	Response format (default: compact). Use "default" for pretty-printed output
`limit`	No	Max rows to return (default: server maxRows setting)
`offset`	No	Row offset for pagination

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.3.0May 4, 2026

addedInput schema / properties / fields

Added value: +{
+  "description": "Column names to include in results (default: all)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / format

Added value: +{
+  "description": "Response format (default: compact). Use \"default\" for pretty-printed output",
+  "enum": [
+    "default",
+    "compact"
+  ],
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Max rows to return (default: server maxRows setting)",
+  "maximum": 10000,
+  "minimum": 1,
+  "type": "number"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Row offset for pagination",
+  "minimum": 0,
+  "type": "number"
+}

First observedv1.1.1Apr 13, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already provide readOnlyHint: true and openWorldHint: true. The description adds value by confirming SELECT-only behavior, but does not disclose other traits like error handling, permission requirements, or how results are returned. Consistent with annotations, so no contradiction.

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?

The description is a single, focused sentence with no wasted words. It is front-loaded with the main purpose and efficiently conveys the core constraint (SELECT only).

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

Completeness2/5

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

Given the lack of an output schema, the description should clarify what the tool returns (e.g., row structure, format details). It does not explain how fields, limit, or offset affect output. The description relies heavily on the schema, which is insufficient for complete context.

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?

Schema coverage is 100%, with all parameters described in the input schema. The description does not add any parameter-specific information beyond what is already in the schema, so baseline 3 is appropriate.

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 'Execute a SQL query' and specifies the restriction to SELECT statements. The title from annotations reinforces this. It distinguishes from sibling tools like batch_execute and execute_card by emphasizing SQL queries.

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?

The description lacks explicit guidance on when to use this tool versus alternatives (e.g., batch_execute, execute_card). It only implies usage for SELECT statements but does not mention when not to use it or provide context about prerequisites.

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

Deploy Server