Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_update_audience

Update a GA4 audience's display name or description while keeping filters unchanged. Use this when only audience metadata needs changing and write access plus confirmation are enabled.

Instructions

[GA4 WRITE] Update an audience (only displayName/description are mutable; filters 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_audience"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoRaw request-body object (JSON) merged OVER the typed fields — use for nested/advanced fields not exposed as flat args.
nameYesFull resource name of the audience to target: "properties/{property}/audiences/{id}".
confirmYesMust be true to apply the change.
updateMaskNoComma-separated field paths to update. Omit to derive from the supplied fields.
descriptionNo
displayNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / body / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / name / description
      Previous value: -"Full resource name of the audience to target, e.g. \"properties/123/…/456\"."New value: +"Full resource name of the audience to target: \"properties/{property}/audiences/{id}\"."
    • removedInput schema / properties / name / minLength
      Removed value: -1
    • addedInput schema / properties / name / pattern
      Added value: +"^\\s*properties\\/\\d+\\/audiences\\/[A-Za-z0-9_-]+\\s*$"
  2. Addedv1.160.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the entire behavioral burden and does a decent job: it discloses the immutability boundary (filters cannot be changed), the authorization prerequisite (GA4_MCP_ENABLE_WRITES=true), and the confirmation guard. It says nothing about return behavior, error modes when attempting to alter an immutable filter, or whether body can shadow name.

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 dense sentences, front-loaded with the write tag and the verb-resource pair, then the mutability constraint and the derived-mask rule. Every clause earns its place; nothing is padding.

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 6-parameter write tool with a free-form nested body object, no annotations, and no output schema, the description covers mutability, mask derivation, auth gating, and confirmation. Minor incompleteness remains around response shape and the interaction between body and typed fields when they conflict.

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 67%, and the description compensates for the gap by explaining the updateMask derivation contract and the case for overriding it with explicit nested paths. It also clarifies that the body is a merge-over layer for nested fields and that only displayName/description are meaningful typed mutation fields, adding real meaning beyond the schema text.

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 an audience") and immediately narrows the scope by declaring only displayName/description mutable while filters are immutable. The [GA4 WRITE] tag plus the mutation constraint makes it unmistakable against ga4_create_audience and ga4_archive_audience without opening any schema.

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 clear operating context: pass only the fields to change, updateMask is derived unless overridden, and it requires GA4_MCP_ENABLE_WRITES=true plus confirm=true. It does not explicitly route the agent to siblings (e.g., use create_audience for new audiences or archive to retire one), so it stops short of full when/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