Skip to main content
Glama

Honeyfield Marketing MCP

GA4: Enhanced measurement

ga4_enhanced_measurement
Destructive

Enhanced-Measurement eines Web-Datenstreams lesen/setzen (Scroll, Outbound, interne Suche, Video, Datei-Downloads, Seitenwechsel, Formular-Interaktionen). action: get | set. settings = Dict von Bool-Flags (z.B. {'scrollsEnabled': true}). streamEnabled ist der Hauptschalter: steht er auf false, misst keine Unterfunktion, auch wenn sie true ist. get liefert alle Flags als true/false. pageChangesEnabled nicht einschalten, wenn die Seite Seitenwechsel schon selbst als page_view meldet (sonst doppelt gezaehlt). data_stream_id aus ga4_list_data_streams. property_id: die GA4-Property des Workspace (andere werden abgelehnt). workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

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": {
      "action": "<action>",
      "property_id": "<property_id>",
      "data_stream_id": "<data_stream_id>"
    },
    "name": "ga4_enhanced_measurement"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
settingsNo
workspaceNo
property_idYes
data_stream_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the destructiveHint=true annotation by explaining the mechanism: streamEnabled is a master switch that nullifies all sub-flags, and pageChangesEnabled can double-count page views. These are exactly the destructive side effects an agent needs before calling set. It stops short of describing failure modes or confirmation requirements for the write path.

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?

Front-loads purpose, then action syntax, then the settings shape, then constraints and warnings — a sensible order with little filler. The parenthetical feature list and the multi-sentence constraint block make it denser than strictly necessary, but nothing is redundant.

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?

An output schema exists, so return values need only light framing, and 'get liefert alle Flags als true/false' suffices. For a destructive write tool it covers prerequisites, the master-switch pitfall, and the double-counting hazard; the remaining gap is an authoritative list of allowed settings keys, which matters because settings is an unconstrained free-form object.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage it documents all five parameters: action semantics (get|set), settings as a bool-flag dict with an example, data_stream_id provenance, property_id constraint, and workspace optionality. The only shortfall is that flag key names are given by German label and two examples rather than an exhaustive key list.

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?

States a concrete verb pair (lesen/setzen) and a concrete resource (Enhanced-Measurement eines Web-Datenstreams), then enumerates the sub-features covered (Scroll, Outbound, interne Suche, Video, Downloads, Seitenwechsel, Formulare). It is clearly distinct from ga4_list_data_streams / ga4_create_data_stream, though it signals that relationship only indirectly via 'data_stream_id aus ga4_list_data_streams'.

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?

Gives real selection guidance: action is get or set, data_stream_id must come from ga4_list_data_streams, property_id must be the workspace's own property (others are rejected), and workspace is optional when only one exists. It even names a when-NOT condition (don't enable pageChangesEnabled if page_view is already sent), but offers no alternative-tool routing beyond the ID source.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources