Skip to main content
Glama
MoonEyes

google-ecommerce-mcp

by MoonEyes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

GA4 realtime

ga4_realtime
Read-onlyIdempotent

Query GA4 realtime data for the last 30 minutes to check tracking changes, such as confirming a page view is counted once, not 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

TableJSON Schema
NameRequiredDescriptionDefault
metricsNoGA4 realtime metrics, e.g. activeUsers, screenPageViews, eventCount
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. 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"
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower. The description adds a real behavioral constraint beyond them — data is limited to the last 30 minutes — plus the return shape, though it says nothing about rate limits, realtime API quotas, or sampling.

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 short, front-loaded sentences: what it is, when it is useful, what it returns. No filler, and the scope constraint (30 minutes) comes before anything else.

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?

With no output schema, the inline return shape ('rows', 'row_count', 'totals', 'metrics') usefully fills that gap, and all three parameters are documented. Only minor omissions remain, such as the realtime API's data freshness or result limits.

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 parameter (metrics, dimensions, property_id defaulting to GA4_PROPERTY_ID) fully documented in the schema. The description adds nothing about parameter syntax or valid values, 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+resource+scope: 'GA4 realtime report for the last 30 minutes'. An agent immediately knows this is the realtime variant versus a historical report, though the sibling ga4_report is never named for direct contrast.

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?

'Useful to check a tracking change, for example that one page view is counted once and not twice' gives a concrete when-to-use scenario. It lacks any when-not-to-use guidance (e.g. use ga4_report for historical windows), so it stops short of the top score.

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