Google Analytics 4 by Get MCP Ads

ga4 get key events

ga4_get_key_events

Read-onlyIdempotent

Retrieve GA4 key events and conversion counts for a property using metadata-aware Data API reports, returning event names and counts for inventory and analysis.

Instructions

Inventory GA4 key events/conversions using metadata-aware Data API reports. Returns best-effort event names and counts.

Input 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.
`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.

Changed2 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / 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.2/5.0

Behavior3/5

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

Annotations already cover readOnly, idempotent, destructive and openWorld, so the safety profile is fully declared. The description adds one genuinely useful trait beyond that — 'best-effort' counts, warning that results may be approximate or incomplete — but it never explains why counts are best-effort (sampling, thresholding, cardinality) or whether the flag list is exhaustive.

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?

Two tight sentences that are front-loaded with the verb and resource; the qualifier 'metadata-aware' and the return note both earn their place. Slightly jargon-heavy phrasing but no filler.

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 shape needn't be described, and the input schema is fully documented. What is missing is the concrete framing an agent needs: how this differs from a generic ga4_run_report keyed on key events, and what 'best-effort' means operationally.

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 documents all five parameters, including the datePreset enum and the interaction with explicit start/end dates. The description adds nothing about parameters, which is acceptable at full coverage but is the baseline score, not a value-add.

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 ('Inventory') and resource ('GA4 key events/conversions'), plus the underlying mechanism (metadata-aware Data API reports). It is clear what the tool returns, though it never names the sibling it competes with (e.g., ga4_run_report with the keyEvents metric), so an agent must infer the differentiation from the name 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 or when-not guidance and no named alternative. The description implies a use case (listing key events/conversions) but leaves the agent to work out why it would pick this over ga4_run_report or ga4_get_event_parameters from the sibling list.

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