Skip to main content
Glama
CW-Codewalnut

Metabase MCP Server

get_metabase_collection

Retrieve a Metabase collection by ID to access its metadata, enabling users to manage and interact with BI assets through the Metabase MCP Server.

Instructions

Retrieve a single Metabase collection by ID.

Args: collection_id (int): ID of the collection.

Returns: Dict[str, Any]: Collection metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The RequestMethod enum used by the handler to specify the HTTP method (GET) for the API request.
    from enum import Enum, auto
    
    class RequestMethod(Enum):
        GET = auto()
        POST = auto()
        PUT = auto()
        DELETE = auto()
    
        def __str__(self):
            return self.name
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it's a retrieval operation. It doesn't disclose behavioral traits like authentication requirements, rate limits, error handling, or whether it's idempotent. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 appropriately sized with a clear purpose statement followed by structured Args and Returns sections. It's front-loaded and wastes no words, though the 'Dict[str, Any]' return type could be slightly more descriptive for non-technical contexts.

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

Completeness3/5

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

Given the tool's low complexity (single parameter) and the presence of an output schema (which covers return values), the description is moderately complete. However, it lacks context on permissions, errors, or relationships to sibling tools, leaving room for improvement in guiding the agent.

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

Parameters4/5

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

The description adds meaningful context for the single parameter by specifying it's an 'ID of the collection', which clarifies its purpose beyond the schema's generic 'Collection Id' title. Since schema description coverage is 0%, this compensation is valuable, though it doesn't detail format constraints (e.g., valid ID ranges).

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 the verb 'Retrieve' and resource 'a single Metabase collection by ID', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_metabase_cards' or 'get_metabase_dashboards' which retrieve other resources, so it doesn't reach the highest score.

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. It doesn't mention sibling tools like 'get_metabase_collections' (if it existed) for listing collections or 'update_metabase_collection' for modifications, leaving usage context implied at best.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CW-Codewalnut/metabase-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server