Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

clients_update

Updates an existing Google Tag Manager client by submitting its full JSON resource and an explicit confirmation, enabling controlled write operations.

Instructions

[WRITE] Update an existing GTM client. 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>",
      "clientId": "<clientId>",
      "bodyJson": "<bodyJson>",
      "confirm": "<confirm>"
    },
    "name": "clients_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to confirm this write operation.
bodyJsonYesFull clients resource as a JSON string.
clientIdYesThe clients ID to update.
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 / clientId / pattern
      Added value: +"^\\d+$"
    • addedInput schema / properties / containerId / 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?

With no annotations, the description carries the full disclosure burden, and it does state this is a write, requires an environment flag and confirm=true. It does not disclose error behavior, whether the update is a full replacement that drops omitted fields, or what happens when fingerprint is absent or stale — significant for a mutation with optimistic locking.

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 the hard requirement, then the payload convention. No filler, though the sentences are terse enough that behavioral details are omitted rather than trimmed.

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 with no annotations and no output schema, the essentials — it is a write, it is gated, it needs a full JSON body — are all present. Missing only edge-case behavior such as fingerprint conflict handling and the shape of the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: bodyJson must carry the FULL resource, implying replacement semantics rather than a patch. Navigation IDs and the confirm flag are covered by the schema itself.

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 client') and the '[WRITE]' tag separates it from the read siblings like clients_get/clients_list. It stops short of explicitly distinguishing it from clients_create or clients_revert, so routing between the mutation siblings is left to inference from the name.

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 concrete preconditions (GTM_MCP_ENABLE_WRITES=true, confirm=true) which is useful gating context. It never says when to prefer this over clients_create (new resource) or clients_revert (undo changes), and gives no when-not guidance.

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