ga4-mcp

Overview Schema Source Related Servers Discussions Admin

ga4_events

Retrieve top Google Analytics 4 events, users, key events, and event values for a property. Specify a date range to analyze event performance.

Instructions

Return top GA4 events, users, key events, and event values.

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_events"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`end_date`	No	yesterday
`start_date`	No	28daysAgo
`property_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 6, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With zero annotations, the description must carry the full behavioral disclosure burden, but it only says 'Return top...' with no mention of ordering, aggregation, date-range semantics, or caveats. No details about authentication, rate limits, or property resolution are provided.

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

Conciseness3/5

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

The one-sentence description is concise and front-loaded with the core result, which is a structural strength. However, it is under-specified for a four-parameter tool with no annotations, so it is not appropriately sized overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, but the description still leaves key invocation details undocumented: acceptable date formats, how limit applies, what determines 'top' ranking, and how property_id is used. The agent must rely on parameter names alone, which is insufficient for reliable invocation.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no meaning for any of the four parameters, including the required property_id, limit, start_date, or end_date. It does not explain date formats, default semantics, or how limit affects results beyond what the schema already shows.

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 the GA4 events resource and says it returns top events, users, key events, and event values, which conveys a clear action and resource. It does not explicitly distinguish itself from siblings such as ga4_top_pages or ga4_run_report, so it misses the top score.

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?

No guidance is given for when to use this tool rather than its siblings like ga4_overview or ga4_run_report. The description simply states what it returns, leaving the agent to infer the appropriate context.

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

Deploy Server