Skip to main content
Glama
Sign In
@takeokunn/metabase-mcp

@takeokunn/metabase-mcp

by takeokunn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_cards

Retrieve saved questions (cards) from Metabase, filtered by collection if needed.

Instructions

Get list of cards (saved questions) in Metabase, optionally filtered by collection

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": "list_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It correctly indicates a read operation ('Get list') and optional filtering. However, it does not disclose pagination behavior, rate limits, or what happens with an invalid collection_id. The description is adequate but minimal for a simple list tool.

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 sentence with 15 words, front-loaded with the verb and resource. Every word earns its place; no fluff.

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?

For a tool with one optional parameter and no output schema, the description covers the essential functionality (listing cards with optional collection filter). It does not mention return format, pagination, or limits, but given the simplicity, this is acceptable.

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 already describes the 'collection_id' parameter as 'Filter by collection ID'. The description adds only the phrase 'optionally filtered by collection', which does not add significant meaning beyond the schema. Schema description coverage is high (100% for the only parameter), 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 'Get list of cards (saved questions)' and the resource 'in Metabase', with optional filtering by collection. This distinguishes it from sibling tools like 'get_card' or 'list_cards_in_dashboards'.

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 provides no guidance on when to use this tool versus alternatives such as 'search', 'get_card', or 'list_cards_in_dashboards'. There is no mention of prerequisites or when not to use it.

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