Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_update_expanded_data_set

Update a GA4 360 expanded data set by supplying only the fields to change; writes require confirmation and write access enabled.

Instructions

[GA4 WRITE] Update an expanded data set (360). Supply fields 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_expanded_data_set"
  }
}

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

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the write gating flags, the write-gate prerequisite, the 360-only scope, and the partial-update semantics implied by deriving updateMask. It says nothing about what happens to fields not supplied, what the response contains, or what permissions are needed beyond the feature flag.

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?

Four short sentences, each carrying distinct information: mutation/scope tag first, then body guidance, then mask derivation, then the two preconditions. Nothing is redundant with the schema or 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 4-parameter mutation tool with no annotations and no output schema, the description covers gating, scope, mask derivation and the escape hatch. Minor gaps remain around untouched fields and response shape, but an agent can invoke it correctly from this text.

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 100%, so the baseline is 3, but the description adds real meaning: it explains the interplay between body fields and updateMask (derived from supplied fields; explicit mask only for nested paths). That is a decision rule the schema alone does not spell out as clearly.

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 opens with a bracketed mutation tag and a specific verb+resource ('Update an expanded data set (360)'), which cleanly separates it from the create/delete expanded-data-set siblings. It stops short of naming any alternative tool, so differentiation is by resource noun only.

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 concrete operating instructions: pass only the fields to change, updateMask is derived automatically, override the mask only for nested paths, and both GA4_MCP_ENABLE_WRITES=true and confirm=true are required. There is no explicit when-not-to-use guidance or routing to other update tools, so it falls short of a 5.

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