Google Analytics 4 by Get MCP Ads

ga4 batch run reports

ga4_batch_run_reports

Read-onlyIdempotent

Batch up to 5 GA4 report requests into one API call to reduce overhead and get all data in a single response.

Instructions

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

Input Schema

TableJSON 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

TableJSON 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.

First observedv2.0.1Sep 23, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful scope context—same property, independence, and one official batch request—but otherwise depends on annotations for the safety profile. It does not disclose details like batch failure semantics or quota behavior.

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 no filler. Every element—count, read-only nature, report type, property scope, and batch mechanism—earns its place and supports agent decision-making.

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?

Given the strong annotations, 100% parameter schema coverage, and presence of an output schema, the description is largely complete for invocation. It could be marginally stronger by naming ga4_run_report as the single-report alternative, but nothing essential for calling the tool is missing.

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 schema already documents propertyId and the reports array in detail. The description's phrases 'independent' and 'same property' add modest context but do not meaningfully expand on the parameter semantics beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Run'), resource ('GA4 Core reports'), scope ('same property'), and batching behavior (1-5 reports in one request). This clearly differentiates it from single-report tools like ga4_run_report and from pivot-based batch tools like ga4_batch_run_pivot_reports.

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

Usage Guidelines4/5

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

The description conveys clear usage context: use this when running 1-5 independent read-only Core reports together for one GA4 property. It does not explicitly name alternatives or state when not to use it, but the context is specific enough to guide selection.

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