Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

transformations_revert

Revert a GTM transformation in a workspace back to its last container-version state, undoing unsaved changes. Requires write access enabled and explicit confirmation.

Instructions

[WRITE] Revert workspace changes to a GTM transformation back to its last container-version state. Requires GTM_MCP_ENABLE_WRITES=true and confirm=true.

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

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to confirm this write operation.
accountIdYesThe GTM account ID.
containerIdYesThe GTM container ID.
fingerprintNoCurrent fingerprint (for optimistic locking).
workspaceIdYesThe GTM workspace ID.
transformationIdYesThe transformations ID to revert.

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.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden: it does disclose that this is a write guarded by an env flag and a confirm flag, which is useful. However, it doesn't say that in-workspace changes are discarded/unrecoverable, whether the revert is itself reversible, or that the fingerprint parameter participates in optimistic locking — all material for a destructive 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?

Two short sentences, front-loaded with a [WRITE] marker and a precise state outcome, followed by the gating requirements. There is no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter mutation with no annotations and no output schema, the description covers the safety gate well but leaves out the consequences of the operation (loss of workspace edits, reversibility, optimistic-locking behavior) that an agent would need to call it safely and interpret the result.

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 all six parameters are already documented in the schema, including confirm and fingerprint. The description restates the confirm requirement but adds no new meaning about accountId, containerId, workspaceId, transformationId, or how fingerprint conflicts are surfaced; 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?

The description states a specific verb and resource ('Revert workspace changes to a GTM transformation') and pins down the resulting state ('back to its last container-version state'), which is meaningfully different from the delete/update siblings. It does not explicitly name an alternative, but the verb plus target state is distinctive enough for an agent to distinguish 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?

Usage is implied (used to undo edits in a workspace) and two real prerequisites are stated: GTM_MCP_ENABLE_WRITES=true and confirm=true. There is no explicit when-not guidance, no mention of which sibling to use if the agent instead wants to modify or delete a transformation, and no note about what happens to pending workspace edits.

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