Retrieve GA4 users active in the last 30 minutes for a property, defaulting to active users by country, with optional metrics and dimensions for custom real-time reports.
Users active in the last 30 minutes. Defaults to activeUsers by country.
| Name | Required | Description | Default |
|---|---|---|---|
| metrics | No | ||
| dimensions | No | ||
| property_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior context — the 30-minute realtime window and that results default to activeUsers by country — but says nothing about rate limits, property permissions, or how defaults are overridden. Adequate but not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with the scope front-loaded and no filler; nothing is wasted. The terseness is efficient, though it leaves the definition thin rather than tight.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 need not be explained, and annotations cover safety. What is missing for a 3-parameter analytics query tool is guidance on valid metric/dimension values, the meaning of property_id, and how this differs from ga4_run_report.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% for all three parameters, so the description must carry the meaning and largely does not. It partially documents the defaults for metrics and dimensions ('activeUsers by country') but never explains property_id, nor what metric/dimension names are valid GA4 values.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific resource and scope ('Users active in the last 30 minutes'), which is clearly a GA4 realtime report and implicitly distinguishes it from the historical ga4_run_report sibling. It never uses a verb like 'report'/'query' and never names the sibling it differs from, so differentiation relies on inference from the 30-minute window.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit when-to-use guidance and no mention of the obvious alternative, ga4_run_report, which is the main routing decision an agent faces here. The realtime scope only weakly implies the use case; nothing states when NOT to use it or what prerequisites (e.g. property access) apply.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.