Skip to main content
Glama
Sign In
Metabase MCP

Metabase MCP

by 1luvc0d3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_cards

Read-onlyIdempotent

List Metabase questions and cards, optionally filtered by collection ID. Returns up to 100 cards for easy browsing and discovery.

Instructions

List questions/cards in Metabase. Returns up to 100 cards. Use search_content for discovery.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
collection_idNoFilter by collection ID
limitNoMax cards to return (default 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already provide readOnlyHint and idempotentHint, so the behavioral burden is light. The description adds useful context about the 100-card limit but does not disclose other traits like rate limits or authorization needs.

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 with no unnecessary words. The purpose is front-loaded and immediately clear.

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?

Given no output schema and the presence of rich annotations, the description adequately covers the tool's functionality. Minor gaps: no mention of ordering, access control, or that results are from user-accessible collections.

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%, so the schema documents both parameters thoroughly. The description adds no new semantic information beyond the schema descriptions, staying at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it lists cards in Metabase, with a specific verb and resource. It references search_content for discovery, distinguishing from that sibling, but does not explicitly differentiate from get_card or list_dashboards.

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?

Provides clear guidance on return limit (up to 100 cards) and suggests search_content for broader discovery, giving context on when to use which tool. However, no explicit when-not-to-use or prerequisites are stated.

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