Google Analytics 4 by Get MCP Ads

ga4 run report

ga4_run_report

Read-onlyIdempotent

Run a GA4 analytics report with intelligent query planning, supporting 52 metrics, 63 dimensions, and auto-pagination.

Instructions

Run a GA4 analytics report with intelligent query planning. Supports 52 metrics, 63 dimensions, auto-pagination. Use ga4://metrics and ga4://dimensions resources for available fields. Max 9 dimensions + 10 metrics per request.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`offset`	No	Optional 0-based row offset for explicit pagination.
`endDate`	No	End date YYYY-MM-DD or relative (today, yesterday)
`metrics`	Yes	Metric keys (e.g., sessions, activeUsers, totalRevenue)
`orderBy`	No	Metric or dimension key to sort by
`startDate`	No	Start date YYYY-MM-DD or relative (7daysAgo, yesterday)
`datePreset`	No	Named reporting period. Use the custom date range when you need exact start and end dates.
`dimensions`	No	Dimension keys (e.g., date, sessionSource, country)
`propertyId`	Yes	GA4 property ID (numeric, e.g., 123456789)
`autoPaginate`	No	When true, omit the limit so the GA4 client paginates through all rows using offset.
`orderDirection`	No	Sort direction for the selected ordering field.	DESC

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

A3.5/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, so the safety profile is covered. The description adds auto-pagination behavior and dimension/metric maxima, but does not discuss quota handling, invalid-field errors, or what 'intelligent query planning' does in practice.

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?

Three sentences with no fluff: purpose, resource source, and constraints. The most important information is front-loaded, and every sentence earns its place.

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 and 100% parameter coverage, the description doesn't need to explain return values or each parameter. It adds the key limits and resource links needed to invoke the tool correctly, though it lacks usage routing guidance.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds cross-parameter constraints ('Max 9 dimensions + 10 metrics per request') and directs agents to ga4:// resources for valid metric/dimension keys, which goes beyond the individual parameter descriptions.

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 states a specific verb+resource: 'Run a GA4 analytics report' with 'intelligent query planning'. It also mentions unique capabilities (52 metrics, 63 dimensions, auto-pagination) that distinguish it from realtime or pivot siblings, though it does not explicitly name those alternatives.

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 explicit guidance on when to use this tool versus ga4_run_realtime_report, ga4_run_pivot_report, or ga4_validate_query. It gives resource-lookup advice (ga4://metrics, ga4://dimensions) and request limits, but no exclusions or alternative routing.

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