Run a read-only GA4 standard report to retrieve analytics data with specified date ranges, dimensions, and metrics.
Run a GA4 standard report (read-only). report = {dateRanges:[{startDate,endDate}], dimensions, metrics, ...}.
| Name | Required | Description | Default |
|---|---|---|---|
| report | Yes | ||
| property_id | Yes | ||
| connection_id | No | ||
| session_token | No |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full disclosure burden, but aside from 'read-only' it says nothing about auth requirements, how connection_id/session_token affect the call, error or empty-result behavior, page limits, or the response shape. This is a minimal safety hint, not adequate behavioral transparency for an API tool with optional auth parameters.
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?
The description is one compact sentence that front-loads the action and then gives an inline shape for the key parameter. Every element earns its place.
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?
For a 4-parameter tool with a nested open-ended report object and no output schema, this description is too thin. Missing date formats, dimension/metric field syntax, optional-parameter behavior, and any return-value guidance make it insufficient for confident invocation.
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?
The inline report = {dateRanges, dimensions, metrics, ...} adds real meaning to the otherwise opaque 'report' object schema. However, the other three parameters (property_id, connection_id, session_token) are not described at all, and the report field list is left open with '...'.
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 opens with a specific verb and resource ('Run a GA4 standard report') and adds 'read-only'. The word 'standard' distinguishes it from the sibling ga4_run_realtime_report without needing to open schemas.
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?
It clearly frames the tool as the standard-report runner, implying it is the choice for ordinary GA4 reporting rather than realtime or administrative/list tools. It does not explicitly say when not to use it or name alternatives, so it stops short of full routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.