Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

gtm_publish_version

Destructive

Publish a reviewed Google Tag Manager container version after explicit user confirmation, ensuring approved changes go live while guarding against accidental releases.

Instructions

Publish a specific GTM container version. Requires separate explicit confirmation after reviewing the version.

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

Input Schema

NameRequiredDescriptionDefault
fingerprintNoVersion fingerprint, recommended for concurrency safety.
version_pathYes
change_summaryYesConcise exact change the user approved in the current request.
user_confirmedYesMust be true only after explicit action-time user confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is largely covered. The description adds one genuinely new behavioral fact beyond that: publication requires a separate explicit action-time confirmation after review. It does not say what publishing does to the currently live container or whether it is reversible, so the added context is modest.

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 sentences, no filler, and the action is front-loaded before the confirmation constraint. Every sentence carries information an agent needs.

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?

For a destructive, non-idempotent mutation the description covers the critical gate (explicit user confirmation, review first) and the schema carries the parameter constraints. What publishing actually affects in the live container is left implicit, but annotations and schema cover most of the remaining burden.

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?

Schema coverage is 75%, with change_summary, user_confirmed and fingerprint documented in the schema. The required version_path has no schema description and the description adds no format or sourcing guidance for it, so the definition does not fully compensate for that gap; baseline 3 is appropriate.

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 (Publish) and resource (a GTM container version), which distinguishes it cleanly from gtm_create_version and gtm_get_version. It does not explicitly name a sibling or contrast behaviors, so it lands at 4 rather than 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 second sentence implies a workflow: review the version, then obtain explicit confirmation and only then publish. That is useful implied guidance, but it never names alternatives (e.g., use gtm_create_version to stage a version) or states when publishing should not be done, so usage guidance is only inferred.

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