Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_update_event_create_rule

Modify conditions or mutations on an existing GA4 event-create rule by passing only the fields to change; the update mask is derived automatically. Requires writes enabled and explicit confirmation.

Instructions

[GA4 WRITE] Update an event-create rule (conditions/mutations 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_event_create_rule"
  }
}

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

TDQS

A3.8/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 well: it discloses that this is a write, that GA4_MCP_ENABLE_WRITES=true and confirm=true are required gates, and that the update mask is auto-derived unless overridden. It does not say whether unspecified fields are preserved or what the response contains, leaving a modest gap for a mutation tool.

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 core action, followed by the invocation rule and then prerequisites. No filler and every clause carries operational 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 4-parameter mutation with no output schema and no annotations, the description covers the action, the masking behavior, and the write gates, all of which the schema documents well. It stops short of describing effects on unspecified fields, but nothing essential for a correct call is missing.

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 the baseline is 3, and the description largely restates the schema's own "omit to derive from supplied fields" note. It does add one piece of real meaning — that an explicit updateMask is needed for nested paths — which is a slight lift over the schema text but not enough to move the dimension.

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?

"Update an event-create rule" gives a specific verb and resource, and the "[GA4 WRITE]" tag flags the mutation class immediately. It is distinguishable from the create/delete event-create-rule siblings by the verb alone, though it never names them 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 an invocation rule ("Pass only the fields to change; updateMask is derived from them") and prerequisites, which implies use on an existing rule rather than creation. However, it gives no explicit when-to-use vs. ga4_create_event_create_rule guidance and no exclusions, so the routing is left partly to inference.

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