Google Analytics 4 by Get MCP Ads

ga4 batch run pivot reports

ga4_batch_run_pivot_reports

Read-onlyIdempotent

Run up to five independent read-only GA4 pivot reports for one property in a single Data API batch request to reduce separate calls and compare results together.

Instructions

Run 1-5 independent read-only GA4 pivot reports for the same property in one official Data API batch request.

Input Schema

Name	Required	Description	Default
`reports`	Yes	Native GA4 report request objects to execute in one batch.
`propertyId`	Yes	Numeric GA4 property ID or properties/{id}.

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv2.1.1Oct 30, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / reports / items / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / reports / items / properties / cohortSpec / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / reports / items / properties / comparisons / items / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / reports / items / properties / dateRanges / items / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / reports / items / properties / dimensionFilter / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / reports / items / properties / metricFilter / $ref
```
Removed value: -"#/properties/reports/items/properties/dimensionFilter"
```
- addedInput schema / properties / reports / items / properties / metricFilter / additionalProperties
```
Added value: +{}
```
- addedInput schema / properties / reports / items / properties / metricFilter / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / reports / items / properties / metricFilter / type
```
Added value: +"object"
```
- removedInput schema / properties / reports / items / properties / pivots / items / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / reports / items / properties / pivots / items / properties / offset / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / reports / items / properties / pivots / items / properties / orderBys / items / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / properties / result / anyOf
```
Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
```
First observedv2.0.1Sep 23, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, openWorld=true, so 'read-only' in the description is largely redundant. It does add two useful constraints beyond the annotations: all reports must target the same property, and the batch is capped at 1-5 reports. Nothing is said about partial failures, per-report errors, or latency in a batch call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler. The cardinality bound and same-property constraint arrive before anything else, and nothing is repeated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The schema is rich and an output schema exists, so return values and parameter formats need no prose. However, for a batch executor the description omits behavior an agent would want before committing: whether reports execute in parallel, what happens if one report fails, and whether quota cost is summed across the batch.

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 both propertyId and the reports array (including nested GA4-native objects) are already documented in the schema. The description adds nothing about parameter syntax or the native GA4 JSON shapes; it only restates the array size bound that maxItems already enforces. Baseline 3 applies.

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 (Run) plus resource (GA4 pivot reports) with clear scope: 1-5 independent reports, same property, one Data API batch request. The 'batch' + 'pivot' combination implicitly separates it from ga4_run_pivot_report (single) and ga4_batch_run_reports (non-pivot batch), but no sibling is named explicitly.

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?

Usage is implied rather than stated: the '1-5 ... same property ... one batch' framing tells an agent this is the multi-report variant, but there is no explicit 'use this instead of X when Y' guidance or any exclusion. An agent must infer the choice against ga4_run_pivot_report and ga4_batch_run_reports.

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