What it does

Details for one event. Optionally break down by a custom property. Volume metric — counts include AI-mediated human browsing (ai_user_action).

Example prompts

Ask:

"Show me details for the signup_started event on mysite.com last 30 days."
"How is the signup_started event split by plan?"
"For the demo_booked event, group by the rep property."

A typical response, grouped by the custom plan property:

Event signup_started, last 30 days, grouped by plan:

  free       182 events
  pro         64 events
  (not set)   14 events

Returns event counts segmented by a property of your choice. The group_by_property argument slices by custom event properties only: any key you attach when firing the event (e.g. plan, variant, source). For built-in dimensions like browser or device type, use breakdown instead; for referrers and UTM tags, use top_referrers and top_sources.

Volume metric: counts include AI-mediated human browsing if the event was fired from a Claude/ChatGPT-fetched page.

To fire custom events from your JS:

window.mcpa('track', 'signup_started', {
  plan: 'pro',
  source: 'pricing_cta'
});

Custom events are a client-side thing: they fire from the visitor's browser via the snippet above. There is also a server-side ingest endpoint (POST /ingest/server, authenticated with your site's ingest secret from /settings), but it exists to capture what the JS snippet can't see: AI crawlers and bots that never execute JavaScript. Human traffic is deliberately dropped on that path so the JS beacon and the middleware don't double-count. Don't route human conversion events through it.

List all event names with list_events first if you're not sure what's being tracked.

Arguments

Name Type Required Description / Default
site_id string required Site identifier from list_sites (8-character base32, e.g. 'wjxayhdd').
event_name string required Custom event name to drill into (case-sensitive). Use list_events to discover available event names. 'pageview' is the auto-tracked default; anything else came from a mcpa('track', name, props) call in the customer's site code.
period string optional Time window. Keywords: today, yesterday, last_7_days, last_30_days, last_90_days, last_12_months. Or a custom date range YYYY-MM-DD..YYYY-MM-DD (inclusive).
default: last_7_days
group_by_property string optional Optional name of a custom property to slice the event by. Example: if events were tracked with mcpa('track', 'signup', {plan: 'pro'}), pass 'plan' here to see counts per plan value.

How to call it directly

If you're integrating from your own code rather than a chat client, this is the JSON-RPC payload:

curl -X POST https://mcp-analytics.com/mcp \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "event_details",
    "arguments": {
      "site_id": "abc12345",
      "event_name": "signup_started"
    }
  }
}'

Token comes from /settings after you sign up. Replace any required arguments above.

Related tools

  • compare_periods: Compare a metric between two periods.
  • top_bots: Named-bot breakdown: which crawlers fetched the site, by canonical bot name (GPTBot, ClaudeBot, PerplexityBot, Googlebot, ...) with their traffic_class and hit counts.
  • breakdown: Breakdown of visits by browser, os, device_type, or country (country empty in MVP).
  • top_user_agents: Top User-Agent strings with their traffic_class.
  • top_pages: Most-viewed URL paths.