Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

templates_update

Update an existing Google Tag Manager template by submitting its full resource as JSON, with write access enabled and confirmation required.

Instructions

[WRITE] Update an existing GTM template. 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>",
      "templateId": "<templateId>",
      "bodyJson": "<bodyJson>",
      "confirm": "<confirm>"
    },
    "name": "templates_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to confirm this write operation.
bodyJsonYesFull templates resource as a JSON string.
accountIdYesThe GTM account ID.
templateIdYesThe templates ID to update.
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.6/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 behavioral burden. It does disclose that this is a write operation requiring an environment flag plus explicit confirmation, which is valuable. However, it never states whether the full-resource payload replaces or merges existing fields, what happens to omitted fields, or how fingerprint conflicts are surfaced – significant gaps for a mutation tool with zero annotation coverage.

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?

Three short sentences, front-loaded with the '[WRITE]' tag and the action, with the gating requirements immediately following. Nothing is redundant, though slightly tighter phrasing could fold the two preconditions together.

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 7-parameter mutation tool with no annotations and no output schema, the description covers the essentials: it is a write, it is gated, and the payload must be a complete resource. The remaining gaps – overwrite semantics, fingerprint conflict behavior, and return shape – are real but secondary for an API-proxy style tool.

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 every parameter is already documented in the schema. The description restates that bodyJson holds the full resource as a JSON string but adds no syntax examples, constraints, or notes on how fingerprint interacts with the update, 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?

The description states a specific verb and resource ('Update an existing GTM template') and the '[WRITE]' prefix signals the mutation class, which separates it from siblings like templates_get and templates_list. It stops short of explicitly distinguishing it from templates_create or templates_revert, but the purpose 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete preconditions that gate invocation: GTM_MCP_ENABLE_WRITES=true and confirm=true. What's missing is guidance on preparation steps, such as fetching the current resource via templates_get or supplying the fingerprint for optimistic locking, and there is no explicit statement of when not to use it.

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