Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

zones_revert

Reverts changes made to a GTM zone in a workspace back to its last container-version state, restoring the zone's previous configuration. Requires write access enabled and confirm=true.

Instructions

[WRITE] Revert workspace changes to a GTM zone 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>",
      "zoneId": "<zoneId>",
      "confirm": "<confirm>"
    },
    "name": "zones_revert"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneIdYesThe zones ID to revert.
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.

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 / workspaceId / pattern
      Added value: +"^\\d+$"
    • addedInput schema / properties / zoneId / 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?

With no annotations, the description carries the full behavioral burden. It does disclose that this is a write, that it is gated behind an environment flag, and that it discards workspace changes in favor of the container version — good context. It does not state whether the discarded changes are recoverable, what happens on a fingerprint conflict, or what permission scope is required.

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 with the [WRITE] marker and the effect statement front-loaded, followed by the hard prerequisites. No filler.

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 essential gating and the effect of the call. It leaves gaps around failure modes (fingerprint mismatch), reversibility, and the response shape, which matter for a destructive operation.

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 six parameters including fingerprint for optimistic locking. The description only restates the confirm=true requirement and adds nothing about fingerprint or ID format, so baseline 3 applies.

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 ('Revert workspace changes to a GTM zone') plus the target state ('last container-version state'), which is far more informative than the bare name. It does not explicitly differentiate itself from sibling revert tools (clients_revert, templates_revert), but the resource scope is unambiguous.

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?

The description gives prerequisites (GTM_MCP_ENABLE_WRITES=true, confirm=true) but no when-to-use versus when-not guidance, e.g. versus zones_update for forward edits. The usage context is implied by 'revert' rather than spelled out.

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