Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

transformations_create

Creates a new Google Tag Manager transformation in a workspace from a JSON resource, requiring write access and explicit confirmation to apply the change.

Instructions

[WRITE] Create a new GTM transformation. Requires GTM_MCP_ENABLE_WRITES=true and confirm=true. Pass the full resource as a JSON string in bodyJson.

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>",
      "bodyJson": "<bodyJson>",
      "confirm": "<confirm>"
    },
    "name": "transformations_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to confirm this write operation.
bodyJsonYesFull transformations resource as a JSON string (e.g. {"name":"...","type":"..."}).
accountIdYesThe GTM account ID.
containerIdYesThe GTM container ID.
workspaceIdYesThe GTM workspace ID.

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

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full burden; it does disclose the write-enable gate and the confirm=true safeguard, which is valuable behavioral context. It omits what happens after creation in GTM (e.g. that the change lives in a workspace and must be published), idempotency, and failure behavior, leaving meaningful gaps for a mutating tool.

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, front-loaded sentences with the [WRITE] marker first, then prerequisites, then the key payload instruction. No filler and nothing 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?

With five required parameters, full schema coverage, and no output schema, the definition covers what an agent needs to construct a valid call: the write gate, the confirm flag, and the bodyJson payload shape. The notable remaining gap is post-creation semantics (workspace/publish lifecycle) for a mutation tool.

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 100%, including descriptions for confirm and bodyJson, so the schema already carries parameter meaning. The description's note that the full resource goes in bodyJson as a JSON string largely restates the schema and adds no syntax or field-level detail beyond it.

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 transformation") and the [WRITE] tag immediately signals the mutating nature, which cleanly separates it from read siblings like transformations_get/list. It does not explicitly contrast with transformations_update, but the create/update distinction is conveyed by the verb itself.

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?

Provides real preconditions for use (GTM_MCP_ENABLE_WRITES=true and confirm=true), which is more than most tools offer. However, it gives no guidance on when to prefer this over transformations_update or what to do if a transformation already exists, so the when-to-use-vs-alternative dimension is only implied.

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