Google Analytics 4 by Get MCP Ads

ga4 batch run reports

ga4_batch_run_reports

Read-onlyIdempotent

Run 1–5 independent read-only GA4 Core reports for the same property in one Data API batch request, reducing separate API calls while preserving per-report settings.

Instructions

Run 1-5 independent read-only GA4 Core 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.

Changed13 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"
```
- addedInput schema / properties / reports / items / properties / offset / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / reports / 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.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds that reports are 'independent' (no chaining between them) and that they share one official API batch call, but says nothing about partial-failure behavior, quota cost, or return shape.

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?

One short sentence, front-loaded with the verb and the key constraint. Every clause (1-5, independent, read-only, same property, one batch request) carries information.

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

Completeness4/5

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

With an output schema, full annotation coverage, and rich parameter descriptions, the definition supplies the essential framing. The main remaining gap is what happens when one report in the batch fails, which is material for a batch tool.

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% and the nested report object is well documented, including native GA4 JSON payloads and date format hints. The description only reinforces the maxItems=5 bound and that propertyId applies across all reports, so it adds little beyond the schema.

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), resource (GA4 Core reports), and scope (1-5 reports for a single property in one batch request). The batch framing implicitly separates it from ga4_run_report, but no sibling is named, so an agent must infer the single-vs-batch distinction.

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?

The '1-5' and 'one batch request' wording implies when to prefer this over the single-report sibling, but there is no explicit when-to-use, when-not, or named alternative. Usage is left to inference from the sibling list.

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