Google Analytics 4 MCP

ga4_list_key_events

Read-only

Lists key events (formerly conversions) on a GA4 property, revealing which events are marked as conversion-worthy. Use it to identify conversion events and then query conversion metrics by name.

Instructions

List key events (formerly conversions) on a GA4 property.

These are the events the client has marked as conversion-worthy. Query conversion metrics via conversions dimension or direct metric names.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "property_id": "<property_id>"
    },
    "name": "ga4_list_key_events"
  }
}

Input Schema

Name	Required	Description	Default
`property_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds useful semantic context about conversion-worthy events and how to query conversion metrics, but it does not disclose operational details like pagination, auth requirements, or property access restrictions.

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?

The description is short, front-loaded, and to the point. The first sentence states the operation and resource, while the additional sentences clarify the semantics and related query usage. Each sentence contributes value, though the final metric-querying hint is slightly tangential to the tool itself.

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?

For a simple one-parameter list tool with readOnly and openWorld annotations plus an output schema, the description is mostly complete. It explains what the key events are and how to think about conversion metrics. The main gap is no explicit guidance on choosing this over the many sibling list tools.

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?

The schema has 0% description coverage and the description does not explain property_id at all. However, the single parameter is self-explanatory and required, so an agent can likely invoke the tool correctly. The description adds no extra meaning beyond the schema's title/type.

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 clearly states the verb 'List' and the exact resource: key events (formerly conversions) on a GA4 property. It distinguishes this tool from sibling list tools because it uniquely identifies client-marked conversion-worthy events and clarifies the legacy naming.

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 gives clear context: these are events the client has marked as conversion-worthy, which tells an agent when listing key events is appropriate. It does not explicitly mention alternative tools or when not to use this tool, so it falls short of full guidance.

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

Deploy Server