ga4-mcp

Overview Schema Source Related Servers Discussions Admin

ga4_realtime

Monitor live user activity in Google Analytics 4 by pulling a realtime report for the past 30 minutes, with options to filter dimensions and metrics to suit your needs.

Instructions

Run a GA4 realtime report for activity from the last 30 minutes.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`metrics`	No
`descending`	No
`dimensions`	No
`property_id`	Yes
`order_by_metric`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 6, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the transparency burden. It makes the read-only, time-boxed report behavior clear, but it does not disclose realtime-specific behaviors such as data latency, metric/dimension compatibility constraints, or property prerequisites. This is adequate for a simple read operation but does not go beyond the obvious.

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?

The single sentence is front-loaded and free of filler, saying exactly what the tool does in one line. It is slightly under-specified for a 6-parameter API, but the wording is appropriately concise for clarifying the core purpose.

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?

With six parameters, no annotations, and sibling tools requiring differentiation, one sentence is not enough context for reliable selection and invocation. The output schema reduces the need to explain returns, but the description still omits usage trade-offs and parameter-level guidance.

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

Parameters1/5

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

Schema description coverage is 0%, yet the description names none of the six parameters and adds no guidance on property_id, metrics, dimensions, ordering, or limit behavior. The schema carries all parameter meaning, so the description fails to compensate for the coverage gap.

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?

The description states a specific verb ('Run'), a specific resource ('GA4 realtime report'), and the distinctive scope of activity from the last 30 minutes. This clearly separates it from sibling tools like ga4_run_report or ga4_overview, which target different time ranges or report types.

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' phrasing implies this tool is for realtime queries, but the description does not explicitly state when to choose it over siblings such as ga4_run_report or ga4_acquisition. There is no when-not-to-use guidance or alternative tool mention, leaving the agent to infer usage from the name and the time window.

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

Deploy Server