Keytomic

List analytics events

list_analytics_events

Read-only

Returns the Google Analytics 4 events of the site’s connected property in a period, most frequent first: for each event name, eventCount, totalUsers (the users who triggered it), eventCountPerUser and keyEvents. isKeyEvent is true when the event counted as a key event in the period. GA4 counts key events only from the day the owner marked the event as a key event, so keyEvents can be lower than eventCount. totalEventNames says how many event names GA4 has for the query, also those past limit; it is not a count of events. Each call reads GA4 directly.

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": {
      "projectId": "<projectId>"
    },
    "name": "list_analytics_events"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Most events to return. totalEventNames says how many GA4 has.
`device`	No	Only sessions on this device category.	all
`country`	No	Only sessions from this country, as an ISO 3166-1 alpha-2 code such as "US". Omit for every country.
`endDate`	No	Last day, YYYY-MM-DD. Defaults to yesterday.
`eventName`	No	Only this event, such as "generate_lead". The name must match exactly, case included. Omit for every event.
`projectId`	Yes	Site to act on, from list_sites. Only its connected Google Analytics property is used.
`startDate`	No	First day, YYYY-MM-DD. Defaults to 28 days ending on endDate, as on the Analytics page.
`trafficSegment`	No	"organic" keeps sessions from the Organic Search channel. "llm" keeps sessions from AI assistants such as ChatGPT, Perplexity and Gemini.	all

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description still adds real behavioral context beyond them: results are ordered most-frequent-first, keyEvents can be lower than eventCount because GA4 counts key events only from the marking date, and totalEventNames includes names beyond the limit. It says nothing about auth needs, rate limits, or failure modes, so it does not fully earn a 4.

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?

Front-loaded with the returned resource and ordering, then the field semantics, then the key-event caveat. Every sentence carries content; the closing 'Each call reads GA4 directly' is short and conveys non-cached freshness, though the paragraph is dense and could be split for scanability.

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?

With 8 parameters and no output schema, the description usefully documents the return shape (eventCount, totalUsers, eventCountPerUser, keyEvents, isKeyEvent, totalEventNames) and the limit/totalEventNames relationship. It is close to complete for a read-only listing tool; only the filtering behavior and any connection prerequisite go unaddressed.

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%, so the schema already explains limit, country, eventName, dates, device and trafficSegment. The description reinforces the semantics of the count fields (totalEventNames is a count of event names, not events) but adds no meaning for the six filter parameters, so the 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 and resource: it returns GA4 events of the site's connected property for a period, most frequent first, and enumerates the per-event fields returned. An agent can tell it apart from a performance-summary tool by the resource itself, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the tool is for event-level breakdowns of a GA4 property over a date period, and 'Each call reads GA4 directly' hints at freshness per call. There is no explicit statement of when to prefer this over search_analytics_query or get_analytics_performance, and no exclusions or prerequisites (e.g. a connected GA property being required).

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

All Keytomic tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?