Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

versions_publish

Publishes a specific Google Tag Manager container version to live after explicit confirmation, making it active in production.

Instructions

[PUBLISH] Publish a specific GTM container version to live. Requires GTM_MCP_ENABLE_PUBLISH=true and confirm=true. ⚠️ This immediately makes the version live in production.

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": {
      "accountId": "<accountId>",
      "containerId": "<containerId>",
      "containerVersionId": "<containerVersionId>",
      "confirm": "<confirm>"
    },
    "name": "versions_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to confirm this publish operation.
accountIdYes
containerIdYes
containerVersionIdYesThe version ID to publish.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / accountId / pattern
      Added value: +"^\\d+$"
    • addedInput schema / properties / containerId / pattern
      Added value: +"^\\d+$"
    • addedInput schema / properties / containerVersionId / pattern
      Added value: +"^\\d+$"
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden, and it does disclose the key trait: publishing immediately makes the version live in production, plus an explicit environment-variable gate and a confirmation flag. It stops short of stating whether a publish can be rolled back or what permissions are required, which are meaningful gaps for an irreversible production mutation.

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?

Three short sentences: the action first, then the gating requirements, then the production warning. Nothing is wasted and the riskiest fact is emphasized rather than buried.

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 four-required-parameter mutation with no annotations and no output schema, the description covers the essential facts an agent needs before calling: the production effect, the enable flag, and the confirm requirement. Only rollback/reversibility and post-publish state are absent, which is a modest gap rather than a blocking one.

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 50%: confirm and containerVersionId are documented in the schema, while accountId and containerId carry only regex patterns. The description reinforces that confirm must be true but adds no meaning for the two identifier parameters, so it neither compensates for the coverage gap nor detracts from the schema baseline.

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 states a specific verb and resource ("Publish a specific GTM container version to live") and tags itself with [PUBLISH], so the agent can identify the operation immediately. It does not, however, distinguish itself from the sibling workspace_create_version_and_publish, which presumably also publishes, leaving a small ambiguity about which publish path to choose.

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?

It gives concrete preconditions (GTM_MCP_ENABLE_PUBLISH=true and confirm=true), which is genuinely useful invocation guidance. But it never says when to prefer this over workspace_create_version_and_publish or versions_set_latest, and offers no when-not guidance, so routing between publish-capable siblings is left to inference.

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