@takeokunn/metabase-mcp

update_snippet

Modify the name, content, description, archived status, or collection of an existing Metabase native query snippet.

Instructions

Update an existing native query snippet 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": "update_snippet"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jul 7, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states 'Update' but omits critical details such as idempotency, error handling (e.g., snippet not found), side effects, or return values. The schema partially covers input fields, but the description adds no behavioral context.

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 extremely concise with a single sentence, which is appropriate for a simple update operation. It is front-loaded and contains no fluff, but it could be slightly expanded to include a bit more context without losing conciseness.

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 tool's complexity (single input parameter with multiple nested fields), lack of annotations, and no output schema, the description is incomplete. It fails to mention expected return value, error conditions, or required permissions. Agents would lack sufficient context for reliable invocation.

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

Parameters2/5

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

Schema_description_coverage is 0%, meaning the description should compensate for parameter meaning. However, the description only mentions 'Update an existing native query snippet' without elaborating on any of the input fields (e.g., which fields are updatable, constraints, or defaults). The schema itself provides adequate descriptions for each property, but the tool description adds no additional semantic value.

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 action ('Update') and the resource ('existing native query snippet in Metabase'). It effectively distinguishes this tool from sibling tools like create_snippet, archive_snippet, get_snippet, and list_snippets, as it focuses on modifying an existing snippet.

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 create_snippet or archive_snippet. It lacks context about prerequisites, typical scenarios, or conditions for appropriate use.

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

Deploy Server