Skip to main content
Glama
MoonEyes

google-ecommerce-mcp

by MoonEyes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

GA4 realtime

ga4_realtime
Read-onlyIdempotent

Check GA4 realtime activity from the last 30 minutes to verify tracking changes, such as confirming a page view is counted once instead of twice.

Instructions

GA4 realtime report for the last 30 minutes. Useful to check a tracking change, for example that one page view is counted once and not twice. Returns {"rows": [...], "row_count": n, "totals": {...}, "metrics": {...}}.

Input Schema

NameRequiredDescriptionDefault
metricsNoGA4 realtime metrics, e.g. activeUsers, screenPageViews, eventCount
client_idNoClient id from clients_list. Required when several clients are registered; empty uses the only client (or the environment variables when there is no client registry)
dimensionsNoGA4 realtime dimensions, e.g. unifiedScreenName, country, deviceCategory
property_idNoNumeric GA4 property id, as listed by ga4_properties; empty uses the configured GA4_PROPERTY_ID (or the client's property)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • addedInput schema / properties / client_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Client id from clients_list. Required when several clients are registered; empty uses the only client (or the environment variables when there is no client registry)",
+  "title": "Client Id"
+}
    • changedInput schema / properties / property_id / description
      Previous value: -"Numeric GA4 property id, as listed by ga4_properties; empty uses the configured GA4_PROPERTY_ID"New value: +"Numeric GA4 property id, as listed by ga4_properties; empty uses the configured GA4_PROPERTY_ID (or the client's property)"
  2. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / property_id
      Added value: +{
+  "default": "",
+  "description": "Numeric GA4 property id, as listed by ga4_properties; empty uses the configured GA4_PROPERTY_ID",
+  "title": "Property Id",
+  "type": "string"
+}
  3. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / dimensions / description
      Added value: +"GA4 realtime dimensions, e.g. unifiedScreenName, country, deviceCategory"
    • addedInput schema / properties / metrics / description
      Added value: +"GA4 realtime metrics, e.g. activeUsers, screenPageViews, eventCount"
  4. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower, and the description adds the meaningful 30-minute staleness window plus the return shape. With no output schema, disclosing {"rows", "row_count", "totals", "metrics"} is real added value; it stops short of noting latency or sampling behavior for realtime data.

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?

Two sentences plus a compact return-shape sketch; purpose and time window come first. Slightly more than strictly necessary given every input is already documented in the schema, but nothing is padded.

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 read-only 4-param tool with full schema coverage and annotations covering safety, this is nearly complete: window, use case and return shape are all present. The one gap is the relationship to ga4_report, which an agent must infer from the word 'realtime'.

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% – metrics, dimensions, client_id and property_id all carry their own guidance, including the client-registry fallback rules. The description adds nothing parameter-specific, so the baseline 3 applies.

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?

States a specific verb+resource ('GA4 realtime report') and pins the scope to 'the last 30 minutes', which is enough to separate it from the sibling ga4_report without opening either schema. An agent immediately knows this is the live-window variant.

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 a concrete motivating scenario ('check a tracking change, e.g. that one page view is counted once and not twice'), which implies when it is useful. However it never names the alternative (ga4_report for historical ranges) or states when not to use it, so the alternative-selection decision is left to inference.

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