Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_update_google_signals

Turn Google Signals on or off for a GA4 property to manage cross-device reporting and demographics collection. Requires writes enabled and per-call confirmation.

Instructions

[GA4 WRITE] Turn Google Signals on or off for a property (cross-device + demographics collection - the user must confirm their privacy disclosures cover it). 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>",
      "state": "<state>",
      "confirm": "<confirm>"
    },
    "name": "ga4_update_google_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYes
confirmYesMust be true to apply the change.
propertyYesGA4 property ID, e.g. "123456789" or "properties/123456789".

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.4/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, requires GA4_MCP_ENABLE_WRITES=true and confirm=true, and warns about the privacy-disclosure implication of enabling collection. It stops short of saying whether disabling is reversible or what happens to previously collected data.

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?

A single front-loaded sentence with a bracketed write tag, a parenthetical clarification, and a trailing requirements clause. Every element earns its place and nothing is padded.

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 3-parameter mutation tool with no annotations and no output schema, the description covers the write gate, the privacy precondition, and the setting's meaning. Only the side effects of toggling (reversibility, historical data impact) are absent.

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 schema already documents property format and confirm. The description adds meaning the schema does not: that confirm is one half of a write gate paired with the environment flag, and that state toggles the same setting on/off. Enum values themselves are left to the schema.

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+resource+scope: turn Google Signals on or off for a GA4 property. The parenthetical clarifies what Google Signals actually is (cross-device + demographics collection), which distinguishes it from neighboring update_* tools like ga4_update_enhanced_measurement or ga4_update_data_retention.

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?

Clearly scoped to enabling/disabling the Signals setting and adds a precondition (user must confirm privacy disclosures cover it) plus the write-gate requirement. It does not name an explicit alternative or say when not to use it, but for a narrowly scoped property-setting toggle there is little ambiguity.

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