Google Analytics 4 by Get MCP Ads

ga4 run funnel recipe

ga4_run_funnel_recipe

Read-onlyIdempotent

Run read-only, configurable GA4 funnel analyses with one report per event or page step and return simple step counts.

Instructions

Run a read-only configurable funnel recipe using one GA4 report per eventName/pagePath step and return simple step counts.

Input Schema

Name	Required	Description	Default
`steps`	Yes	Ordered funnel steps. Each step needs eventName or pagePath.
`metric`	No	Metric used for the analysis; use a name from the platform metric catalogue.	activeUsers
`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)

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.

Changed3 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / steps / items / additionalProperties
```
Removed value: -false
```

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

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond them: the tool fans out to one GA4 report per step (implying cost proportional to step count) and returns only 'simple step counts' rather than full breakdowns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the read-only nature plus the return shape come early. It is efficient, though arguably too terse for a six-parameter tool with a nested steps array.

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?

An output schema exists, so return values need not be spelled out, and parameter documentation is complete in the schema. However, the description leaves important gaps for a funnel tool: whether step counts are sequential (with drop-off) or independent per-step totals, and the quota cost of one report per step.

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 every field, including the nested step object and enums, is documented in the schema. The description reinforces that steps key off eventName/pagePath but adds no format, default, or constraint detail beyond what the schema already states. Baseline 3 applies.

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') and resource ('configurable funnel recipe') and explains the mechanism: one GA4 report per eventName/pagePath step. It does not name the obvious sibling ga4_run_advanced_funnel_report, so an agent must infer the distinction from 'simple step counts' alone.

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 when-to-use guidance, no exclusions, and no mention of alternatives such as ga4_run_advanced_funnel_report or ga4_run_report. The only hint is the word 'recipe', leaving the agent to guess when this funnel variant is the right choice.

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