Monitor realtime active users segmented by page, country, and device to identify immediate traffic trends and user behavior.
Get realtime active users broken down by page, country, and device
| Name | Required | Description | Default |
|---|---|---|---|
| propertyId | Yes | GA4 Property ID | |
| accountId | No | GA4 account ID for multi-account setups |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations are absent, so description must cover behavioral traits. It indicates a read operation ('get') but does not mention permissions, rate limits, or data freshness. The description is adequate for a simple query tool.
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?
Single sentence efficiently conveys purpose. It is front-loaded with the main action and scope, though it could benefit from a second sentence on output format.
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?
No output schema exists, so the description should clarify return value structure. It mentions breakdowns but not whether results are paginated or aggregated. Adequate for a simple tool but leaves ambiguity.
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 coverage is 100% with descriptions for both parameters. The description does not add meaning beyond the schema; it mentions dimensions (page, country, device) but these are not parameters, so no enhancement.
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?
The description clearly states the verb 'get', resource 'realtime active users', and scope 'broken down by page, country, and device'. It distinguishes the tool from siblings focused on Bing or other analytics functions.
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?
No explicit guidance on when to use this tool versus alternatives. It implies use for realtime data, but lacks comparison to related analytics tools like analytics_trends or analytics_top_pages.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.