Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_update_property

Updates a GA4 property's display name, time zone, currency, or industry category. Use it to correct property settings, with writes enabled and per-call confirmation required.

Instructions

[GA4 WRITE] Update a GA4 property (displayName / timeZone / currencyCode / industryCategory). 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": {
      "property": "<property>",
      "confirm": "<confirm>"
    },
    "name": "ga4_update_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYes
propertyYesGA4 property ID, e.g. "123456789" or "properties/123456789".
timeZoneNo
updateMaskNo
displayNameNo
currencyCodeNo
industryCategoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / property / minLength
      Removed value: -1
    • addedInput schema / properties / property / pattern
      Added value: +"^\\s*(properties\\/)?\\d+\\s*$"
  2. Addedv1.160.0

TDQS

A3.8/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 two most important traits: this performs a write and is gated behind an env flag plus an explicit confirm flag. It says nothing about required OAuth scopes, whether omitted fields are left unchanged, or what updateMask does, all relevant for a mutation.

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?

Two compact sentences with the write tag and field list front-loaded and the prerequisites immediately after. Dense but no wasted words; slightly more could be spent on updateMask given the low schema coverage.

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 tool with no annotations, no output schema, and 14% schema coverage, the description covers the safety gate well but leaves updateMask and the partial-update contract unexplained, which an agent needs to call it correctly.

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 only 14% (only 'property' is documented), so the description must compensate. It names four updatable fields but omits confirm, updateMask, and does not explain mask semantics or partial-update behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (update a GA4 property) and enumerates the mutable fields (displayName / timeZone / currencyCode / industryCategory), which separates it from siblings like ga4_create_property and ga4_delete_property.

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?

Gives concrete preconditions for use: the GA4_MCP_ENABLE_WRITES=true environment flag and confirm=true. It does not state when to prefer this over e.g. ga4_update_account or other update tools, so the alternative-selection guidance is implicit rather than explicit.

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