Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_update_channel_group

Update a GA4 custom channel group by supplying its grouping rule or display name. Change only the fields you need; the update mask is derived automatically from them.

Instructions

[GA4 WRITE] Update a custom channel group (supply groupingRule/displayName via body). 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_channel_group"
  }
}

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 channel group to target: "properties/{property}/channelGroups/{id}".
confirmYesMust be true to apply the change.
updateMaskNoComma-separated field paths to update. Omit to derive from the supplied fields.

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 channel group to target, e.g. \"properties/123/…/456\"."New value: +"Full resource name of the channel group to target: \"properties/{property}/channelGroups/{id}\"."
    • removedInput schema / properties / name / minLength
      Removed value: -1
    • addedInput schema / properties / name / pattern
      Added value: +"^\\s*properties\\/\\d+\\/channelGroups\\/[A-Za-z0-9_-]+\\s*$"
  2. Addedv1.160.0

TDQS

A3.9/5.0
Behavior4/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 substantial work: it marks this as a write, discloses the environment-flag and confirm gating, explains the updateMask derivation, and warns that the raw body is merged OVER typed fields. It doesn't describe failure modes or what happens to untouched fields, so it stops short of full behavioral disclosure.

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?

It is a single tight block, front-loaded with the [GA4 WRITE] marker and the verb+resource, then the payload hint, then the mask behavior, then the gating requirements. Parenthetical nesting makes it dense but every clause carries information.

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 mutating tool with a free-form nested body object, no annotations, and no output schema, the description covers the essentials: write gating, mask derivation and override, and body-over-typed-field precedence. Only edge-case behavior on partial updates is left unstated.

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 100%, so all four parameters are already documented, including the derivation rule for updateMask and the body-merge semantics. The description restates that derivation rather than adding new syntax or format detail, so baseline 3 is appropriate.

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 names a specific verb and resource ("Update a custom channel group") and notes the key payload fields (groupingRule/displayName). It is immediately distinguishable from ga4_create_channel_group and ga4_delete_channel_group by the operation, though it never explicitly contrasts with 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 tells the agent to pass only the fields to change and that updateMask is derived automatically, with an escape hatch for nested paths. It also states the preconditions (GA4_MCP_ENABLE_WRITES=true and confirm=true). What's missing is explicit when-to-use vs the create/delete siblings, but for an update tool the context is clear.

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