Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

transformations_update

Update an existing GTM transformation by submitting its full JSON resource; write access and confirm=true are required.

Instructions

[WRITE] Update an existing 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>",
      "transformationId": "<transformationId>",
      "bodyJson": "<bodyJson>",
      "confirm": "<confirm>"
    },
    "name": "transformations_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to confirm this write operation.
bodyJsonYesFull transformations resource as a JSON string.
accountIdYesThe GTM account ID.
containerIdYesThe GTM container ID.
fingerprintNoCurrent fingerprint (for optimistic locking).
workspaceIdYesThe GTM workspace ID.
transformationIdYesThe transformations ID to update.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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 / transformationId / 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.8/5.0
Behavior4/5

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

With no annotations, the description carries the safety profile itself and does so credibly: it flags the operation as a write, discloses the feature-flag gate and the confirm requirement, and states that the full resource must be supplied in bodyJson, implying replacement semantics rather than a partial merge. It stops short of explaining concurrency behavior (the fingerprint/optimistic-locking parameter) or what happens on a failed write.

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, zero filler, with the [WRITE] tag and the mutation verb front-loaded before the prerequisites and payload instructions. Every sentence contributes a distinct piece of information.

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 seven-parameter write tool with no annotations and no output schema, the description covers the essentials an agent needs to call it safely: write classification, environment gate, confirm flag, and full-resource payload semantics. The remaining gap is the optimistic-locking behavior of fingerprint and the result of a conflict, which the schema names but does not explain.

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%, so the schema already documents all seven parameters including the ID patterns and fingerprint. The description only restates the bodyJson and confirm semantics, adding the useful nuance that bodyJson must be the *full* resource, but nothing about fingerprint usage or how IDs are obtained.

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 ("Update an existing GTM transformation") and marks it with a [WRITE] tag, so the mutation intent is unambiguous. It does not explicitly contrast with siblings such as transformations_create or transformations_revert, but the verb itself is discriminating enough for an agent to pick it.

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 a concrete precondition (GTM_MCP_ENABLE_WRITES=true and confirm=true), which tells the agent when the call will succeed. However, it never names an alternative for related tasks — e.g., use transformations_get to read current state first, or transformations_revert to restore a prior version — so the agent must infer when this is the right tool over its siblings.

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