Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

ga4_run_realtime_report

Run read-only GA4 realtime reports with named dimensions and metrics, filters, ordering, and limits to inspect current property activity.

Instructions

Run a read-only GA4 realtime report using named dimensions and metrics.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
metricsYes
order_bysNo
dimensionsNo
property_idYesNumeric GA4 property ID or properties/{id}.
metric_filterNoOptional GA4 FilterExpression for metrics.
minute_rangesNo
dimension_filterNoOptional GA4 FilterExpression for dimensions.
return_property_quotaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully declares 'read-only' and implies the realtime data window, but says nothing about the realtime lookback period, cardinality caps (4 dimensions, 4 metrics, 2 minute ranges), rate limits, required scopes, or what happens when limits are exceeded.

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?

A single front-loaded sentence with no filler and no redundancy. It is efficient, though the efficiency comes partly from omitting information rather than from tight editing.

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

Completeness2/5

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

For a 9-parameter tool with nested filter objects, array caps, no annotations, and no output schema, one sentence is far from sufficient. An agent cannot tell the realtime window, the format of minute_ranges or order_bys entries, or the shape of the returned report.

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

Parameters2/5

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

Schema description coverage is only 33% across 9 parameters, so the description should compensate but does not. It mentions only that dimensions and metrics are 'named' (implying API names like eventName rather than display names), leaving minute_ranges, order_bys, metric_filter, dimension_filter, limit, and return_property_quota entirely unexplained outside 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?

States a specific verb and resource: 'Run a read-only GA4 realtime report.' The word 'realtime' distinguishes it in substance from the sibling ga4_run_report, but the description never names that sibling or states the distinction explicitly, so an agent must infer it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no mention of when a standard report (ga4_run_report) would be preferable. The agent is left to infer from the adjective 'realtime' alone that this is for recent, non-historical data.

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