Skip to main content
Glama
kLOsk

AdLoop: Google Ads, Reddit Ads & GA4

by kLOsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Analytics realtime report

run_realtime_report
Read-only

Display current active users and events from GA4 to verify tracking fires correctly after code changes. Returns metric headers and rows over the last 30 minutes.

Instructions

Run a GA4 realtime report showing current active users and events.

Useful for checking if tracking is firing correctly after code changes. Returns the dimension and metric headers and one row per dimension combination over the realtime window (the last 30 minutes).

Google Analytics Data API: https://developers.google.com/analytics/devguides/reporting/data/v1 and Admin API: https://developers.google.com/analytics/devguides/config/admin/v1

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
metricsNoGA4 realtime metric API names, e.g. activeUsers, eventCount. Defaults to ["activeUsers"].
dimensionsNoGA4 realtime dimension API names, e.g. unifiedScreenName, eventName, country, deviceCategory.
property_idNoGA4 property as "properties/123456789" (see get_account_summaries). If empty, uses the default from config.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.27.1
    • addedInput schema / properties / dimensions / description
      Added value: +"GA4 realtime dimension API names, e.g. unifiedScreenName,\neventName, country, deviceCategory."
    • addedInput schema / properties / metrics / description
      Added value: +"GA4 realtime metric API names, e.g. activeUsers, eventCount.\nDefaults to [\"activeUsers\"]."
    • addedInput schema / properties / property_id / description
      Added value: +"GA4 property as \"properties/123456789\" (see\nget_account_summaries). If empty, uses the default from config."
  2. Addedv0.13.2
  3. Removedv0.13.0
  4. First observedv0.9.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the 30-minute realtime window and the return shape (dimension/metric headers plus one row per dimension combination).

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?

Front-loaded with the core action, followed by the use case and then the return shape, all in four short sentences with no filler. The trailing API documentation links are slightly extraneous but minimally costly.

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?

An output schema exists so return values needn't be explained, yet the description still characterizes them helpfully. Combined with annotations covering safety and the schema covering all parameters, an agent has what it needs, with only the missing sibling differentiation as a gap.

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%, so the schema already documents metrics, dimensions, and property_id including the properties/123456789 format and defaults. The description adds no additional parameter meaning, which is the expected baseline when the schema does the work.

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 (run a GA4 realtime report) and scopes it to the realtime window (last 30 minutes), which separates it conceptually from the historical run_ga4_report sibling. It never names that sibling explicitly, so an agent must infer the realtime-vs-historical split from the title alone.

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?

"Useful for checking if tracking is firing correctly after code changes" gives one concrete usage scenario, which is more than nothing. However, it offers no exclusions or alternatives (e.g. run_ga4_report for historical data, validate_tracking for deeper validation), so an agent picking among the many report siblings still has to guess.

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