@takeokunn/metabase-mcp

run_preview_embed_dashboard_pivot_dashcard_query

Executes a pivot query for a preview of an embedded dashboard dashcard in Metabase. Uses token authentication for secure access.

Instructions

Run a pivot query for a preview embedded dashboard dashcard in Metabase

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": {
      "input": "<input>"
    },
    "name": "run_preview_embed_dashboard_pivot_dashcard_query"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jul 7, 2026

TDQS

C2.5/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It says 'run a pivot query' but does not state whether this is read-only, what side effects exist, what authentication is needed, or what the response looks like. The word 'preview' might imply read-only, but it's not explicit.

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

Conciseness2/5

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

The description is a single brief sentence, but it is under-specified. While it avoids verbosity, it sacrifices important information, making it insufficient for an agent to use correctly.

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

Completeness1/5

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

Given the complexity (nested input, many sibling tools, no output schema, no annotations), the description is severely incomplete. It does not explain what a pivot query is, what 'preview embedded' means, how parameters relate, or what the tool returns. The agent lacks critical context to invoke it correctly.

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

Parameters1/5

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

Schema description coverage is 0%: the description does not mention any of the three required parameters (token, card_id, dashcard_id). The nested input object is completely unexplained. With zero coverage, the description fails to add any meaning beyond the schema.

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 action (run a pivot query) and the resource (preview embedded dashboard dashcard). The name itself is very specific, and the description aligns with it, distinguishing from siblings like run_preview_embed_dashcard_query (non-pivot) and run_embed_dashboard_pivot_dashcard_query (non-preview).

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 on when to use this tool versus alternatives. The description provides no context about prerequisites, when a pivot query is needed, or how this differs from similar tools like run_preview_embed_dashcard_query. The agent is left to infer from the name alone.

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

Deploy Server