Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

gtag_config_update

Updates an existing Google Tag Manager gtag configuration using a full JSON resource, with write access enabled and per-call confirmation required.

Instructions

[WRITE] Update an existing GTM gtag config. 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>",
      "gtagConfigId": "<gtagConfigId>",
      "bodyJson": "<bodyJson>",
      "confirm": "<confirm>"
    },
    "name": "gtag_config_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to confirm this write operation.
bodyJsonYesFull gtag configs resource as a JSON string.
accountIdYesThe GTM account ID.
containerIdYesThe GTM container ID.
fingerprintNoCurrent fingerprint (for optimistic locking).
workspaceIdYesThe GTM workspace ID.
gtagConfigIdYesThe gtag configs ID to update.

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 / gtagConfigId / 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?

With no annotations, the description carries the full burden and does disclose the write-gating mechanism (env flag plus confirm=true) and that the full resource body is expected, implying replacement rather than partial patch. It omits consequences of the overwrite, whether the fingerprint is required for optimistic locking conflicts, and what a failed write returns — material 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] marker and action verb, with no filler. It could be slightly better structured by grouping the prerequisites together, but nothing is wasted.

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 output schema, the description covers the action, the access gate, the confirmation requirement, and the body format — enough to call it correctly. Missing are conflict/fingerprint behavior and overwrite consequences, which keep it from being fully complete.

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, including the fingerprint's optimistic-locking role and confirm's requirement. The description's only added semantics is the emphasis on passing the full resource in bodyJson, which the schema largely already states; 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?

States a specific verb and resource ('Update an existing GTM gtag config') and the [WRITE] tag marks the mutation class, which separates it from gtag_config_get/list/create/delete siblings by implication. It stops short of naming an explicit alternative, but the operation 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?

Gives hard preconditions for invoking it (GTM_MCP_ENABLE_WRITES=true and confirm=true), which is genuinely useful gating. It does not say when to choose this over a sibling update tool or what to do if the config does not yet exist (create), so usage guidance is implied 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