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

@takeokunn/metabase-mcp

by takeokunn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_collection_items

Retrieve items like cards and dashboards from a collection. Filter by type, limit results, and paginate with offset.

Instructions

Get items (cards, dashboards, etc.) within a collection (supports "root" for root 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": "get_collection_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.4/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 fails to explicitly state that this is a read-only operation, safe to call, or whether it requires any permissions. The description merely restates the purpose without addressing side effects, rate limits, or error conditions.

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 exceptionally concise—a single sentence that conveys the essential purpose and a key usage detail. Every word earns its place with no redundancy.

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?

The description covers the core functionality, item types, and root collection support. While it omits details on pagination behavior (though limit/offset are in schema) and error handling, it is sufficiently complete for a simple list retrieval tool given the schema covers parameters.

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 schema provides full descriptions for all parameters (id, limit, models, offset), so the description adds little beyond reinforcing the special 'root' value for id. Baseline 3 is appropriate as the schema coverage is high.

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 tool's action (Get items) and resource (within a collection). It also specifies the supported content types (cards, dashboards, etc.) and highlights the special 'root' value for the root collection, which distinguishes it from siblings like get_root_collection_items.

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 the many sibling tools such as get_collection_tree, get_collection_permissions, or get_root_collection_items. The description does not specify prerequisites, alternatives, or when not to use this tool.

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