Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

templates_revert

Reverts GTM template workspace changes to the last container-version state, requiring write access and explicit confirmation.

Instructions

[WRITE] Revert workspace changes to a GTM template 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>",
      "templateId": "<templateId>",
      "confirm": "<confirm>"
    },
    "name": "templates_revert"
  }
}

Input Schema

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

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 / templateId / 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 exist, so the description carries the full load. It does disclose the write nature and both gating requirements, which is real added value. It omits the consequences — that uncommitted workspace edits are discarded, whether the revert is reversible, and what happens on a fingerprint mismatch (optimistic locking is only named in the schema).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the [WRITE] marker and the action, no filler. It is efficient but slightly clipped at the point where a consequence clause would earn its place.

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

Completeness2/5

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

For a destructive mutation with no annotations and no output schema, essential context is missing: what state is restored, that pending workspace changes are lost, and how concurrency failures (fingerprint) manifest. Prerequisites alone are insufficient for safe invocation.

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. The description adds meaning only for confirm (the write gate); fingerprint and the ID parameters get nothing beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb+resource+scope: revert GTM template workspace changes to the last container-version state. The [WRITE] tag and the sibling set (templates_create/delete/update/get) make the distinct action obvious.

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?

Prerequisites (GTM_MCP_ENABLE_WRITES=true, confirm=true) imply when the tool is callable, but there is no guidance on when to revert versus templates_update or the other *_revert siblings, and no warning about when reverting would be a mistake.

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