Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_run_realtime_report

Run a read-only GA4 Data API realtime report to confirm events from the last ~30 minutes and verify a tag is firing during live QA.

Instructions

Run a read-only GA4 Data API Realtime report (events in roughly the last 30 minutes). Useful to confirm a tag is firing right now during live QA. Read-only — never writes. Requires the analytics.readonly scope.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (default 100).
metricsYesMetric names, e.g. ["eventCount","totalUsers"]. At least 1, max 10.
propertyYesGA4 property ID, e.g. "123456789" or "properties/123456789".
dimensionsNoDimension names, e.g. ["eventName","date"]. Max 9. Omit for a metric-only report.

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. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it declares read-only semantics twice, states the required analytics.readonly scope, and discloses the ~30-minute data window. It stops short of quota/rate-limit behavior or the shape of returned rows.

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?

Three short sentences, front-loaded with the action and scope before the use case and constraints. The only minor redundancy is restating read-only as 'Read-only — never writes' after opening with 'read-only'.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter read tool with no output schema and no annotations, the definition covers mutability, auth scope, and the temporal data window well. It does not describe what the response contains (rows keyed by dimensions with metric values), which an agent needs to plan a call correctly.

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 description coverage is 100%, with each of property, metrics, dimensions, and limit documented inline including examples and bounds. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 specific verb and resource ('Run a read-only GA4 Data API Realtime report') and clarifies the resource scope with '(events in roughly the last 30 minutes)', which is what distinguishes it from the historical ga4_run_report sibling. It never names that sibling explicitly, so the differentiation is inferable rather than stated.

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?

Gives one concrete when-to-use scenario ('confirm a tag is firing right now during live QA'), which is genuinely helpful. However, it offers no exclusions and no routing guidance toward ga4_run_report for historical data, leaving the agent to infer the boundary.

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