Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

gtm_create_version

Destructive

Create a Google Tag Manager container version from a workspace to publish approved changes. Consumes the workspace and requires explicit user confirmation before execution.

Instructions

Create a GTM container version from a workspace. This consumes the workspace and requires explicit confirmation.

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": {
      "workspace_path": "<workspace_path>",
      "name": "<name>",
      "change_summary": "<change_summary>",
      "user_confirmed": "<user_confirmed>"
    },
    "name": "gtm_create_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
notesNo
change_summaryYesConcise exact change the user approved in the current request.
user_confirmedYesMust be true only after explicit action-time user confirmation.
workspace_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds the critical consequence that the workspace is consumed by the call and that user confirmation is mandatory. It still does not say whether the workspace contents survive elsewhere or what the response contains, so it is not a 5.

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?

Two short sentences with zero filler, leading with the action and following with the two consequences that matter. Nothing could be removed without losing information.

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?

For a destructive, non-idempotent mutation the description covers the two highest-risk facts (workspace consumption, confirmation). However, with no output schema and undocumented path/name parameters, an agent still lacks guidance on how to construct workspace_path and what a successful call yields.

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 coverage is only 40% across five parameters; workspace_path, name, and notes carry no schema descriptions and the tool description adds nothing about their expected form (e.g. a GTM resource path). Only change_summary and user_confirmed are documented, and that documentation lives in the schema, not the description.

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?

States a specific verb and resource ('Create a GTM container version') plus the source ('from a workspace'), which is enough to tell it apart from gtm_create_workspace (creates the workspace) and gtm_publish_version (publishes an existing version). It does not explicitly name those siblings, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'requires explicit confirmation' clause implies a prerequisite gate for calling it, which is useful when-to-use context. There is no explicit when-not guidance and no routing between this and gtm_publish_version or the listing tools, so the agent must infer the workflow position.

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