Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

zones_update

Update an existing Google Tag Manager zone by submitting its full JSON resource; writes require the write flag enabled and confirm=true.

Instructions

[WRITE] Update an existing GTM zone. 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>",
      "zoneId": "<zoneId>",
      "bodyJson": "<bodyJson>",
      "confirm": "<confirm>"
    },
    "name": "zones_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneIdYesThe zones ID to update.
confirmYesMust be true to confirm this write operation.
bodyJsonYesFull zones resource as a JSON string.
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.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it labels the operation as a write, discloses the two environment/argument preconditions, and states that the full resource must be supplied in bodyJson, which signals full-replacement semantics rather than a partial patch. It does not mention optimistic locking/fingerprint handling or what the call returns.

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 operation type and write-gate front-loaded before the bodyJson instruction. Every sentence earns its place.

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 7-parameter mutation with no output schema, the description covers the safety gate and payload shape but omits the success response, the meaning of fingerprint for optimistic locking, and whether the update replaces or merges the existing zone. Adequate but with clear gaps.

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 seven parameters are already documented, and the description mostly restates them (confirm=true, full resource in bodyJson). It adds no syntax, format, or edge-case detail beyond the schema, so the baseline of 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?

The description opens with a specific verb and resource ("Update an existing GTM zone"), and the "[WRITE]" tag plus "existing" separates it from zones_create, zones_get, zones_list, and zones_delete without opening a schema. It stops short of naming any sibling explicitly, so it lands just below the top of the scale.

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 gating condition (GTM_MCP_ENABLE_WRITES=true and confirm=true), which is more actionable than implied usage. However, it offers no routing guidance against alternatives such as zones_get (to fetch the current resource) or zones_revert, and no when-not-to-use cases.

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