Google Analytics 4 by Get MCP Ads

ga4 run pivot report

ga4_run_pivot_report

Read-onlyIdempotent

Run read-only GA4 Data API pivot reports with native filters, ordering, multiple date ranges, quota state, and up to 250,000 pivot cells. Specify an explicit limit per pivot.

Instructions

Run a read-only GA4 Data API pivot report with native filters, ordering, quota state, multiple date ranges, and up to 250,000 pivot cells. Every pivot requires an explicit limit.

Input Schema

Name	Required	Description	Default
`report`	Yes	Native GA4 report request object for this endpoint.
`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 / report / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / report / properties / cohortSpec / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / report / properties / comparisons / items / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / report / properties / dateRanges / items / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / report / properties / dimensionFilter / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / report / properties / metricFilter / $ref
```
Removed value: -"#/properties/report/properties/dimensionFilter"
```
- addedInput schema / properties / report / properties / metricFilter / additionalProperties
```
Added value: +{}
```
- addedInput schema / properties / report / properties / metricFilter / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / report / properties / metricFilter / type
```
Added value: +"object"
```
- removedInput schema / properties / report / properties / pivots / items / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / report / properties / pivots / items / properties / offset / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / report / 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.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds meaningful behavior beyond annotations: quota state is returned, multiple date ranges are supported, and there is a 250,000-cell cap with a mandatory explicit limit per pivot. It does not explain pagination/offset behavior or error conditions, but it does more than repeat annotations.

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?

The description is two sentences, front-loads the core purpose, and uses the remaining space for the most important constraint (explicit limit per pivot). No sentence is wasted, and it is appropriately sized for a complex tool whose schema carries detailed parameter 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, rich annotations, and full schema description coverage, the description supplies the essential calling context: it is a read-only pivot report, quota state is available, and every pivot needs an explicit limit. The main remaining gap is routing guidance versus batch pivot reports and plain reports, but an agent has enough information to invoke this tool correctly.

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 fully documented, including required pivot limit, date range formats, and filter expression types. The description reinforces the explicit-limit requirement and mentions multiple date ranges, but adds little syntax or semantic detail beyond what the schema already provides. Baseline 3 is appropriate.

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?

The description names a specific verb and resource: 'Run a read-only GA4 Data API pivot report.' The word 'pivot' distinguishes it from the plain ga4_run_report sibling, but it does not explicitly contrast itself with ga4_batch_run_pivot_reports or other report variants, leaving some sibling differentiation to inference.

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 by 'pivot report' — an agent can infer this is the tool for pivoted output rather than a flat report. However, the description never states when to choose this over ga4_run_report, ga4_batch_run_pivot_reports, or ga4_validate_query, nor does it specify exclusions or prerequisites beyond the limit requirement.

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