Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_update_custom_dimension

Update a GA4 custom dimension's display name, description, or ads-personalization setting by passing only the fields to change; writes must be enabled and confirmed.

Instructions

[GA4 WRITE] Update a custom dimension (parameterName and scope are immutable). Pass only the fields to change; updateMask is derived from them (override with an explicit updateMask for nested paths). 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": {
      "name": "<name>",
      "confirm": "<confirm>"
    },
    "name": "ga4_update_custom_dimension"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull resource name of the custom dimension to target: "properties/{property}/customDimensions/{id}".
confirmYesMust be true to apply the change.
updateMaskNoComma-separated field paths to update. Omit to derive from the supplied fields.
descriptionNo
displayNameNo
disallowAdsPersonalizationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / name / description
      Previous value: -"Full resource name of the custom dimension to target, e.g. \"properties/123/…/456\"."New value: +"Full resource name of the custom dimension to target: \"properties/{property}/customDimensions/{id}\"."
    • removedInput schema / properties / name / minLength
      Removed value: -1
    • addedInput schema / properties / name / pattern
      Added value: +"^\\s*properties\\/\\d+\\/customDimensions\\/[A-Za-z0-9_-]+\\s*$"
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. Addedv1.160.0

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden and does well: it discloses that this is a write, requires an environment flag and explicit confirmation, and that some fields cannot be changed. It does not cover failure behavior, idempotency, or what a successful 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense and front-loaded: the write marker, the action, the immutability caveat, and the preconditions all land in three short sentences. The nested parentheses make it slightly harder to scan but no clause 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 mutation tool with no annotations and no output schema, the description supplies the critical safety and precondition context an agent needs before calling. The remaining gap is return-value behavior and the semantics of the three undocumented optional fields.

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 coverage is 50%, and the description's updateMask note largely restates what the schema already says ("Omit to derive from the supplied fields"), adding only the nested-path override nuance. The undocumented parameters (description, displayName, disallowAdsPersonalization) get no explanation in either place, though their names are largely self-evident.

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?

The description opens with a specific verb and resource ("Update a custom dimension") and immediately adds a scoping constraint that parameterName and scope are immutable. The verb distinguishes it cleanly from the create/archive siblings without needing to name them.

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 clear invocation guidance ("Pass only the fields to change") plus hard preconditions (GA4_MCP_ENABLE_WRITES=true and confirm=true), which tells the agent exactly when the call will succeed. It stops short of naming alternatives such as archive+recreate for immutable fields, so no explicit exclusion path is offered.

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