Skip to main content
Glama

Read a tab of the Events page

get_event_analytics
Read-only

One tab of the dashboard's Events page with the exact numbers behind it. overview: totals against the previous period and every event with users, count, previous count, worked and failed, plus key events. screens: views, users and time per screen. taps: taps per screen and element. broken_taps: dead and rage taps. sessions: length, bounce, entry and exit screens, platforms, versions, recent sessions. devices: app version, OS, model, country, locale and more. Days are in UTC. Tables are capped at 60 rows.

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": {
      "view": "<view>"
    },
    "name": "get_event_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewYes
rangeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: days are in UTC, and tables are capped at 60 rows — the truncation limit is exactly the kind of caveat an agent needs to avoid over-reading results. It lacks any note on permissions, empty periods, or error behavior, so not a 5.

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 summary sentence is front-loaded and each view gets a compact clause with no filler. The enumeration is dense but scannable; the only soft spots are vague tails like 'and more' in the devices list, which dilute the value of the enumeration.

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 no output schema, the description bears the burden of conveying return content, and it does so by listing fields per view. Combined with the UTC and 60-row-cap notes, an agent has enough to call it and interpret results. It stops short of covering default range behavior or what an empty tab returns.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry parameter meaning — and it largely does, expanding each of the six view enum values into concrete metrics (users, count, previous count, worked/failed for overview; dead and rage taps for broken_taps). The range parameter (24h/7d/30d/90d) is never explained, and 'previous period' only hints at comparison semantics, leaving one of two parameters under-specified.

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 and resource: 'One tab of the dashboard's Events page with the exact numbers behind it,' and then enumerates all six views, so an agent knows exactly what surface this covers. It does not explicitly name a sibling (e.g. get_analytics or get_store_analytics) to contrast against, which keeps it just below a 5.

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 implied rather than stated: the view enumeration makes clear which tab to pick when you want screens, taps, sessions, or devices, but there is no explicit when-to-use / when-not-to-use guidance and no reference to alternatives in the sibling list. An agent can infer the right selection from the view names, but must do so itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources