Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_acknowledge_user_data_collection

Acknowledge a GA4 property owner’s required user privacy disclosures and rights so write operations such as creating links or MP secrets can proceed.

Instructions

[GA4 WRITE] Acknowledge that the property owner has the required user privacy disclosures/rights. Some operations (e.g. creating certain links or MP secrets) require this once. 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>",
      "confirm": "<confirm>"
    },
    "name": "ga4_acknowledge_user_data_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYes
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.160.0

TDQS

A4/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 it is gated behind an environment flag plus an explicit confirm argument, and that the requirement is a one-time acknowledgement. It does not describe the failure mode (e.g. error when already acknowledged) or what the call returns, which keeps it from a 5.

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?

Three short sentences, front-loaded with the bracketed write tag and the core action, followed by the trigger condition and the prerequisites. No filler or repetition; every clause carries information an agent needs.

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 two-parameter, no-output-schema, no-annotation tool, the definition covers purpose, when it is needed, and both gating prerequisites. What remains thin is the outcome side: no indication of what success looks like, whether the call is idempotent, or which permissions the caller needs beyond being the property owner.

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 50%: 'property' is documented in the schema with its ID pattern, while 'confirm' has no schema description. The description partially compensates by explaining that confirm=true is required to perform the write, giving the parameter real meaning beyond its bare boolean type. The property parameter's format adds nothing beyond the schema.

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: acknowledging that the property owner has the required user privacy disclosures/rights, and tags it as a GA4 WRITE. This is a distinctive, one-of-a-kind operation that cannot be confused with the create/update/list siblings. It falls short of 5 only because it never explicitly contrasts itself with any named alternative.

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 states when this is needed: 'Some operations (e.g. creating certain links or MP secrets) require this once,' which tells an agent this is a prerequisite step rather than a routine call. It also gives the gating conditions (GA4_MCP_ENABLE_WRITES=true and confirm=true). It does not say what to do if the acknowledgement was already performed or whether re-calling is safe.

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