Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_update_data_redaction

Update client-side data redaction for a GA4 web data stream by enabling email redaction and redacting specified URL query parameters. Requires write mode and confirm=true.

Instructions

[GA4 WRITE] Update a WEB data stream's client-side data redaction: email redaction and URL query-parameter redaction (with the parameter key list). 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>",
      "dataStreamId": "<dataStreamId>",
      "confirm": "<confirm>"
    },
    "name": "ga4_update_data_redaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to apply the change.
propertyYesGA4 property ID, e.g. "123456789" or "properties/123456789".
dataStreamIdYesData stream ID (numeric) or "dataStreams/{id}".
queryParameterKeysNoQuery params to redact, e.g. ["email", "phone"].
emailRedactionEnabledNo
queryParameterRedactionEnabledNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden and does disclose the key traits: this is a write ([GA4 WRITE] tag), it is restricted to WEB streams, and it is environment-gated plus confirm-gated. It does not say what happens to redaction settings that are omitted (left unchanged vs reset), whether the change is reversible, or what permissions beyond the env flag are needed.

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?

A single front-loaded sentence with the tag first, the action second, and the prerequisites last; nothing is wasted. The nested parenthetical about the parameter key list is slightly dense but still readable.

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 six-parameter mutation tool with no annotations and no output schema, the description covers purpose, write gating, stream type, and the redaction fields, which is close to sufficient. The main residual gap is behavior for omitted toggles and the response shape, but no output schema exists to offload that.

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 67%, so the schema already documents the required property, dataStreamId, and confirm parameters. The description adds real meaning only for the redaction fields, clarifying that queryParameterKeys is the key list used by query-parameter redaction; it says nothing about emailRedactionEnabled/queryParameterRedactionEnabled being independent toggles.

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 (Update) and a narrowly scoped resource: a WEB data stream's client-side data redaction, covering exactly email redaction and URL query-parameter redaction. That scope implicitly separates it from the broader ga4_update_data_stream, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the two gating conditions for use (GA4_MCP_ENABLE_WRITES=true and confirm=true), which tells the agent when the call can succeed. There is no explicit when-not-to-use guidance and no routing to alternative tools for related settings such as data retention or the overall data stream.

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