Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

ga_realtime

Read-only

Fetches Google Analytics 4 realtime active-user counts for the last 30 minutes, grouped by dimensions such as country, screen, or device category.

Instructions

GA4 realtime report (last 30 minutes): active users by a dimension such as country, unifiedScreenName, deviceCategory.

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": {
      "propertyId": "<propertyId>"
    },
    "name": "ga_realtime"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
metricsNo
dimensionsNo
propertyIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true and openWorldHint=true already cover the safety profile (read-only, external data). The description adds meaningful behavior beyond that: the fixed 30-minute lookback window and the fact that output is active users grouped by a dimension. It does not disclose rate/quota limits, the restricted set of valid realtime dimensions/metrics, or the response shape, which are real behavioral gaps for a GA4 realtime API.

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 dense sentence with the time window and output shape front-loaded and zero filler. It reads as a fragment rather than a full sentence, but nothing is wasted and the key scoping fact comes first.

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 zero schema coverage, the description is only partially complete: it explains what the report contains and the 30-minute window, but leaves the required propertyId and limit undocumented and says nothing about the return structure. An agent could probably invoke it with defaults but would be guessing on propertyId format and row limits.

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 0%, so the description carries the full burden. It does add useful semantics for two parameters by giving dimension examples (country, unifiedScreenName, deviceCategory) and implicitly confirming activeUsers as the default metric. But the required propertyId (GA4 property identifier format) and the limit parameter (pagination/row cap) are entirely undocumented, leaving half the parameters opaque.

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: 'GA4 realtime report (last 30 minutes): active users by a dimension'. This clearly distinguishes it from the batch ga_run_report or ga_overview and scopes the data window. It does not name the sibling alternatives explicitly, keeping it below a 5.

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?

The 'last 30 minutes' scope implicitly tells the agent this is for near-live data, which is useful context. However, there is no explicit when-to-use guidance against ga_run_report, ga_overview, or ga_get_metadata, and no stated preconditions (e.g., property must exist, realtime dimension restrictions).

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