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

@takeokunn/metabase-mcp

by takeokunn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_collections

List all collections (folders) in your Metabase instance. Optionally filter by namespace to refine results.

Instructions

Get list of all collections (folders) 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": "list_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.6/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 carry the burden. It implies a read operation but does not explicitly state that it is read-only, safe, or whether authentication is required. No mention of pagination or side effects.

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

Conciseness4/5

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

The description is a single concise sentence with no wasted words. However, it omits the optional filter parameter, which would improve utility without adding much length.

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 annotations and output schema, and only one optional parameter, the description is insufficient. It does not explain the return format, pagination, or any additional context needed for effective use.

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?

The input schema description coverage is 0%, and the tool description does not add any meaning beyond the schema. The description fails to mention the optional 'namespace' filter, which is crucial for filtering. The description should compensate for the low schema coverage but does not.

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 gets a list of all collections, with the parenthetical '(folders)' adding context. It differentiates from sibling tools like 'get_collection' (single) and 'create_collection', but could be more specific by mentioning the optional namespace filter.

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 is provided on when to use this tool versus alternatives such as 'get_collection' for a specific collection or 'search' for searching collections. There is no mention of prerequisites or context.

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