Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

ga4_run_report

Run a read-only GA4 report over a date range using named dimensions and metrics, so you can pull analytics data without changing your property.

Instructions

Run a read-only GA4 report for a date range using named dimensions and metrics.

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>",
      "start_date": "<start_date>",
      "end_date": "<end_date>",
      "metrics": "<metrics>"
    },
    "name": "ga4_run_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
metricsYes
end_dateYesYYYY-MM-DD, today, yesterday, or NdaysAgo.
order_bysNo
dimensionsNo
start_dateYesYYYY-MM-DD, today, yesterday, or NdaysAgo.
property_idYesNumeric GA4 property ID or properties/{id}.
currency_codeNoOptional ISO 4217 currency code.
metric_filterNoOptional GA4 FilterExpression for metrics.
keep_empty_rowsNo
dimension_filterNoOptional GA4 FilterExpression for dimensions.
return_property_quotaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden; 'read-only' usefully substitutes for a readOnlyHint, but nothing is said about result size limits (the schema defaults to 10,000 rows with a 100,000 cap), pagination via offset, quota behavior hinted at by return_property_quota, or how filter expressions affect results. For a 13-parameter reporting call this leaves the agent guessing about cost and result shape.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity borders on under-specification given the tool's parameter surface.

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?

Thirteen parameters, nested objects, no annotations, and no output schema demand far more than one sentence. An agent cannot learn from this definition how to paginate, constrain row counts, or construct the filter objects that are central to a GA4 report.

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

Parameters2/5

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

Schema description coverage is only 46%, so the description should compensate, but it only gestures at date range, dimensions, and metrics. It adds no meaning for order_bys, dimension_filter, metric_filter, limit, offset, keep_empty_rows, currency_code, or return_property_quota, and does not explain the GA4 FilterExpression structure that nested filter objects require.

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 and resource ('Run a read-only GA4 report') plus the scope ('for a date range using named dimensions and metrics'), which an agent can distinguish from ga4_run_realtime_report by the absence of 'realtime'. It stops short of explicitly contrasting with the realtime sibling, so not a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites such as authentication or property access, and no routing to alternatives like ga4_get_metadata for discovering valid dimension/metric names or ga4_run_realtime_report for live data. The only usage signal is the word 'read-only'.

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