Google Analytics 4 by Get MCP Ads

ga4 run advanced funnel report

ga4_run_advanced_funnel_report

Read-onlyIdempotent

Run advanced GA4 funnel reports with optional breakdown dimensions and next-action analysis, falling back to step counts when advanced data is unavailable.

Instructions

Run the GA4 Data API v1alpha runFunnelReport endpoint with optional breakdown/next-action, falling back to read-only step counts if unavailable.

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.
`steps`	Yes	Ordered funnel steps using eventName, pagePath, or fieldName+fieldValue
`endDate`	No	End date YYYY-MM-DD or relative (today, yesterday)
`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.	last28days
`propertyId`	Yes	GA4 property ID (numeric, e.g., 123456789)
`isOpenFunnel`	No	Allow users to enter at any funnel step instead of requiring the first step.
`breakdownLimit`	No	Maximum breakdown values to include in the funnel response.
`nextActionLimit`	No	Maximum next actions returned for each funnel step.
`visualizationType`	No	Supported funnel visualization mode.	STANDARD_FUNNEL
`breakdownDimension`	No	Optional breakdown dimension, e.g. deviceCategory or sessionDefaultChannelGroup
`nextActionDimension`	No	Optional next action dimension, commonly eventName
`fallbackToStepCounts`	No	If the advanced funnel is unavailable, return independent step counts with the limitation made explicit.

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

Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behaviorikuha. The description adds meaningful behavioral context: it calls out the v1alpha endpoint (implying experimental status) and discloses the fallback to read-only step counts when the advanced funnel is unavailable. This goes beyond what annotations state without contradicting them.

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 sentence packs the endpoint, key optional features, and the fallback behavior. It is front-loaded and contains no filler. Every clause earns its place.

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?

With 13 parameters and an output schema, the description plus the schema cover most operational detail. However, the description lacks any usage-context guidance (e.g., when to choose this over the simpler funnel recipe) and doesn't hint at pagination or rate-limit handling beyond the schema's limit parameter. It is adequate but not fully complete for a complex 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?

Parameter descriptions in the schema are complete (100% coverage) and already explain each field. The description only highlights 'optional breakdown/next-action', which maps to breakdownDimension and nextActionDimension, adding minimal interpretive value. This matches the baseline for full schema coverage.

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 endpoint ('GA4 Data API v1alpha runFunnelReport') and action ('Run'), plus distinctive features (breakdown/next-action, fallback to step counts). It is clear about what the tool does, though it does not explicitly contrast with the sibling ga4_run_funnel_recipe, so it stops short of a 5.

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?

The description gives no guidance on when to prefer this tool over alternatives like ga4_run_report or ga4_run_funnel_recipe, nor any exclusions based on property capabilities or date-range constraints. The only hint is the fallback behavior, which is about runtime behavior rather than selection criteria.

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