Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_enhanced_measurement_get

Retrieve enhanced measurement settings for a GA4 web data stream to verify whether scrolls, outbound clicks, site search, video engagement, file downloads, and forms are enabled.

Instructions

Get the enhanced measurement settings for a specific WEB data stream (scrolls, outbound clicks, site search, video engagement, file downloads, form interactions). Only valid for web streams. Served via the Admin API v1alpha surface (not yet in v1beta). Read-only.

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>"
    },
    "name": "ga4_enhanced_measurement_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
propertyYesGA4 property ID, e.g. "123456789" or "properties/123456789".
dataStreamIdYesThe data stream ID (numeric) or full "dataStreams/{id}" suffix.

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
  3. Removedv1.350.0
  4. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/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 most of the job: it declares the operation read-only, discloses the Admin API v1alpha surface (a real behavioral caveat about stability/availability vs v1beta), and states the web-stream-only precondition. It stops short of permission scopes or failure behavior for non-web streams, which would be needed for 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 tight clauses, front-loaded with the action and resource, then the settings enumeration, then the two constraints. No filler or restated title.

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 read-only getter with full schema coverage and no output schema, the description covers purpose, precondition, and API surface adequately; the enumerated settings partially substitute for return-value documentation. A brief note on the response shape or behavior for a non-web stream would close the remaining gap.

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% and both parameters are pattern-documented with format examples, so the schema does the heavy lifting and baseline 3 applies. The description adds only the implicit constraint that dataStreamId must reference a web stream, which is meaningful but minor.

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?

The description names a specific verb (Get) and resource (enhanced measurement settings), pins the scope to a specific WEB data stream, and enumerates the concrete settings returned (scrolls, outbound clicks, site search, video engagement, file downloads, form interactions). That enumeration clearly separates it from the mutation sibling ga4_update_enhanced_measurement without needing the other schema.

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?

"Only valid for web streams" gives an explicit when-not condition, which is the main usability trap for this tool. It does not explicitly name the update counterpart for changing these settings, so routing guidance is implied rather than stated.

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