Tool reference

What the MCP server can answer.

Start with list_projects for ids, and get_insights for open-ended questions — it returns conclusions with evidence, corrected for the traps the raw tools warn about.

Analysis

ToolAnswers
get_project_summaryHeadline numbers against the prior window.
get_event_trendA time series for direction over time.
list_top_eventsWhich events fire most.
break_down_eventsSplits by country, plan, signup_source, and more.
analyse_funnelOrdered conversion between events, sequenced per user.
get_retentionCohort retention by first-seen period.
get_user_distributionHow activity spreads across users.
compare_cohortsWhether doing X predicts doing Y, activity-adjusted.
list_persons / get_personRecently active users and one user's history.

Money and acquisition

ToolAnswers
get_revenueWhat was paid, by whom, by source and store.
get_subscriptionsThe lifecycle: base, movement, trials, churn, refunds, realized LTV.
get_marketing_performanceImpressions, installs, and spend by channel.
compare_channelsAcquisition against activation and revenue, by channel.

The fix-verify pair

ToolDoes
create_annotationDrops a release marker at a point in time. Needs mcp:annotate.
compare_windowThe same window before and after a marker: totals, error counts, per-event deltas. Flags an after-window that has not fully elapsed, so an undercount is never read as a drop.

Two habits the tools themselves will remind you of: use analyse_funnel for any conversion question (dividing event counts overweights heavy users), and treat an empty revenue result as "nothing connected", never as "no sales".