Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

versions_create

Snapshot a GTM workspace into a new container version without publishing, so you can preserve and share a reviewable checkpoint of your tag configuration.

Instructions

[WRITE] Create a new GTM container version from a workspace (checkpoint). Requires GTM_MCP_ENABLE_WRITES=true and confirm=true. This takes a snapshot of the workspace into a versioned checkpoint without publishing.

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>",
      "workspaceId": "<workspaceId>",
      "confirm": "<confirm>"
    },
    "name": "versions_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoVersion name/label.
notesNoVersion notes / change description.
confirmYes
accountIdYes
containerIdYes
workspaceIdYes

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 / workspaceId / pattern
      Added value: +"^\\d+$"
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it flags a write operation, discloses the two gating requirements, and states the key side-effect boundary (snapshot only, no publish). It does not say whether repeated calls create duplicates or what the response contains.

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 with the [WRITE] tag front-loaded, prerequisites second, and the effect boundary last. No filler or repetition.

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 mutation tool with six parameters and no output schema, it covers the essentials an agent needs: write gating, confirmation, source object, and the fact that nothing is published. Return shape and ID parameter meaning remain undocumented but are lower risk.

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 description coverage is 33%; name and notes are documented in the schema, but accountId, containerId, workspaceId and confirm have no schema descriptions. The description only adds meaning for confirm (must be true) and the workspace relationship, leaving the ID parameters unexplained beyond their pattern.

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 new GTM container version from a workspace') and adds the clarifying parenthetical 'checkpoint'. The trailing clause 'without publishing' implicitly separates it from versions_publish, though it never names that sibling.

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

Usage Guidelines4/5

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

Gives concrete preconditions (GTM_MCP_ENABLE_WRITES=true, confirm=true) and implies the branch point versus publishing with 'without publishing'. It does not explicitly say when to choose this over versions_publish or versions_set_latest, leaving that 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