Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_update_account

Updates a Google Analytics 4 account's display name when write access is enabled and confirmation is provided.

Instructions

[GA4 WRITE] Update a GA4 account (displayName). Requires GA4_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>",
      "displayName": "<displayName>",
      "confirm": "<confirm>"
    },
    "name": "ga4_update_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYes
accountIdYes
displayNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / accountId / minLength
      Removed value: -1
    • addedInput schema / properties / accountId / pattern
      Added value: +"^\\s*(accounts\\/)?\\d+\\s*$"
  2. Addedv1.160.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 does carry the important behavioral facts: this is a write, it is gated behind an environment flag, and it needs an explicit confirm flag. It stops short of stating permissions needed, whether the update is reversible, whether unmentioned account fields are preserved, or what the response contains.

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 compact sentences, front-loaded with the WRITE tag and the affected resource, followed immediately by the preconditions. Nothing is redundant and nothing buries the critical write gate.

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 3-required-parameter mutation with no annotations and no output schema, the description covers the safety gate but leaves account ID semantics, failure modes, and post-update state undocumented. It is adequate to invoke safely but not 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 0%, so the description must carry parameter meaning. It identifies displayName as the updated value and implies confirm is the write-guard, but accountId is explained only by the schema's regex pattern, and confirm's exact semantics (opt-in to mutation) are implied rather than stated.

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 a GA4 account) and narrows the mutable field to displayName, which separates it from the many update_* siblings that target access bindings, properties, audiences, etc. It does not explicitly name an alternative, but the resource noun is unambiguous enough for an agent to discriminate.

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 real preconditions — GA4_MCP_ENABLE_WRITES=true and confirm=true — which tells the agent when the call will succeed. It offers no guidance on when this tool should be chosen over ga4_delete_account or the property-level equivalents, so scope selection is only implied.

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