FullSession

MUTATES DATA: creates a dashboard and optionally fills it in one step — with brand-new charts (newCharts) and/or existing library charts (existingChartIds). Max 15 charts. Confirm the plan with the user before calling. Each chart needs a chartType and a querySpec. querySpec uses a `measure` with exact names (e.g. 'totalSessions', not 'sessions') and, for breakdown/table charts, a `groupBy` (e.g. ['country']). Layout: the dashboard is a 3-column grid — columns are x=0,1,2; width w is 1–3 with x+w<=3; height h is always 1. Simplest and recommended: leave layout out on every chart and they auto-place left-to-right, top-to-bottom. Titles: chart titles have no time window (no '(7d)', 'last 30 days', etc.) — cards carry no fixed time filter; the window is applied when the dashboard is viewed.

create_dashboard

MUTATES DATA: saves a new named audience segment on a site. Build the filters with generate_segment_from_prompt first — do not hand-write them. This tool runs the real filter → query conversion before saving and rejects filters that don't actually resolve to anything. Confirm the segment name and audience with the user before calling.

create_segment

Aggregated click/frustration stats for a single element (by CSS selector or visible text) across all sessions on a page, plus the sessions where it was rage/dead/error clicked with replay URLs. Use get_page_heatmap (clicks mode) first to discover element selectors.

get_element_interactions

MUTATES DATA — DESTRUCTIVE: soft-deletes a chart from the site's library, removing it from every dashboard that shows it. Only call after the user has explicitly confirmed deleting this specific chart by name.

delete_card

MUTATES DATA — DESTRUCTIVE: permanently deletes a funnel and its precomputed results. Only call after the user has explicitly confirmed deleting this specific funnel by name.

delete_funnel

MUTATES DATA — DESTRUCTIVE: soft-deletes a dashboard. The charts on it stay in the site's chart library (they are not deleted). Only call after the user has explicitly confirmed deleting this specific dashboard by name.

delete_dashboard

MUTATES DATA — DESTRUCTIVE: permanently deletes a segment. Any alert, dashboard, or Lift AI goal built on it will lose that reference. Only call after the user has explicitly confirmed deleting this specific segment by name.

delete_segment

MUTATES DATA — DESTRUCTIVE: permanently deletes a saved heatmap view. The underlying session data is untouched; only the saved page/device/segment/time-range bookmark is removed. Only call after the user has explicitly confirmed deleting this specific heatmap by name.

delete_heatmap

Draft a funnel's ordered steps from a plain-language description (e.g. 'home page, then pricing, then signup'), using the same generator as the FullSession dashboard. Uses an AI model to draft it. Nothing is saved; show the returned stepNames to the user to confirm the sequence. This is the way to build funnel steps for create_funnel/update_funnel (the steps format is deeply nested to write by hand); pass `steps` through unchanged.

generate_funnel_steps_from_prompt

Draft a segment filter from a plain-language audience description (e.g. 'mobile visitors from Germany who added to cart'), using the site's custom events and attributes. Uses an AI model to draft it. Nothing is saved; the user can apply it in the FullSession segment builder.

generate_segment_from_prompt

MUTATES DATA: updates a saved chart's title, description, type, or querySpec. Only the provided fields change; querySpec, when given, replaces the whole spec (preview it first with the matching read tool for this chartType — get_metric/get_trend/get_breakdown/get_page_ranking/get_feedback_snapshot/get_page_flow). The change affects every dashboard showing this chart. Confirm with the user before calling.

update_card

Paginated session recordings from a recommendation's evidence, split by whether the user hit the issue (affected/notAffected) and whether they converted — with replay URLs. E.g. "users who hit this issue but still converted" = type affected + outcome converted.

get_recommendation_sessions

Get the details of one session: metadata, a summary of its signals, and a step-by-step timeline of what the visitor did, plus a replay link. Optional extra sections: pages, errors, clicks, network, forms. Use to explain what happened in a specific session.

get_session

Per-form interaction stats aggregated across sessions: impressions, completion rate, and abandonment rate, with the pages each form appears on. Note: stats are per form element — field-level data isn't available. To watch users abandon a specific form, follow up with search_sessions using filters.hasAbandonedForm.

get_form_analytics

Aggregated interaction data for one page across all matching sessions, in one of three modes: clicks (per-element click/rage/dead/error breakdown ranked by frustration), scroll (how far down the page users scroll), or movement (mouse-movement density zones and hotspots). Use get_element_interactions to deep-dive one element from the clicks result. Use for questions like 'what do people click on the pricing page?' or 'how far do visitors scroll on /blog?'

get_page_heatmap

One-call health summary for a site over a time window: total sessions, unique visitors, average duration and page count, frustration totals (rage/dead/error clicks), and top landing pages, countries and devices. Start here before drilling into search_sessions, heatmaps or funnels.

get_site_overview

The friction issues Lift AI found for a goal — what to fix, why, where (page + funnel steps), predicted lift, and the evidence 2×2 session counts — plus the latest run's conversion prediction inline. Pass a recommendation's id to get_recommendation_sessions for the underlying replays. Use for questions like 'what should we fix to improve conversions?'

get_ai_recommendations

List the websites (sites) the connected account can access, with each site's ID and URL. Call this first when the user hasn't said which site they mean, or to match a site name or URL to its siteId.

list_sites

Lift AI is FullSession's AI analysis that finds what blocks conversions in a funnel. Lists Lift AI goals (funnel + KPI targets the AI analyzes for friction) with each goal's latest run prediction. The entry point before get_ai_recommendations — use it to find the goalId.

list_ai_goals

The dashboards visible to the authenticated user on a site, with their charts (cards) and grid layouts. Pass a dashboard id to get_dashboard_data to compute its numbers.

list_dashboards

Conversion funnels defined on a site with their step names, base segment and status. The entry point before get_funnel_analysis / get_funnel_sessions — use it to find the funnelId.

list_funnels

List the saved audience segments on a site (named visitor filters, e.g. 'Mobile users in the US'), with the fields each one filters on. Segments with usableAsSegmentId=true can be passed as segmentId to get_page_heatmap so results match the dashboard for that audience. Use create_segment/update_segment/delete_segment to manage them.

get_segments

The site's chart library: every saved chart/card with its type, measure/groupBy querySpec, and description — whether or not it sits on a dashboard. Use get_metric/get_trend/get_breakdown/get_page_ranking/get_feedback_snapshot/get_page_flow to compute a chart definition ad hoc. Use add_card_to_dashboard to place a saved one.

list_cards

Saved heatmap view definitions (page/device/segment/time-range combinations users bookmarked in the dashboard). Use get_page_heatmap with the same page/device/segment/window to compute the actual data. Use create_heatmap/update_heatmap/delete_heatmap to manage them.

get_heatmaps

A dashboard's full definition: its charts (cards) with chart type, querySpec (measure/groupBy), and grid layout. Use get_dashboard_data to compute the actual numbers.

get_dashboard

Profile and visit history of one identified visitor (by userId or email): first and last seen, devices, top countries, latest custom fields, and every session with replay links. Use when the user asks about a specific customer or visitor.

get_user_sessions

Step-by-step conversion for a funnel: users per step, drop-off, median time and interactions between steps, plus overall entrants/finishers/conversion rate. Optionally break down by country/device/browser/os, or compare saved segments against the funnel's audience. Use for questions like 'where do users drop off in the checkout funnel?' The user sees a funnel card with breakdown tabs (device/country/browser/os), so call this once; only call again with a breakdown if the user explicitly asks about one.

get_funnel_analysis

MUTATES DATA: attaches an existing chart from the site's library to a dashboard (max 15 charts per dashboard). The chart itself is unchanged and can sit on several dashboards at once. Reversible with remove_card_from_dashboard.

add_card_to_dashboard

Ranks every page on a site by rage, dead, or error clicks so you can find the highest-friction pages without checking each one. Follow up with get_page_heatmap (clicks mode) on a page to see which elements cause the frustration. Use for questions like 'which pages have the most rage clicks this week?'

compare_pages_by_frustration

MUTATES DATA: detaches a chart from a dashboard. The chart stays in the site's library and on any other dashboards — this only removes the placement. The inverse of add_card_to_dashboard.

remove_card_from_dashboard

MUTATES DATA: updates a dashboard's name, description, or privacy. Only the provided fields change. Confirm with the user before calling.

update_dashboard

MUTATES DATA: saves a page/device/segment/time-range combination as a named heatmap view in the dashboard. Confirm the page path and audience with the user before calling.

create_heatmap

Find session recordings on a site that match filters (time window, user, page, country, device, frustration signals…). Returns short summaries with frustration counts, a replay link, and a sessionId for get_session. Use for questions like 'show me sessions with rage clicks on /checkout yesterday'. signals.rageClickBursts counts bursts of rapid clicking (one burst is several clicks), so it is lower than the individual rage-click totals from get_site_overview and the heatmap tools.

search_sessions

Searches the site's crawled, indexed knowledge sources (documentation, marketing pages, pricing, support content, etc. — declared via the Daleel Knowledge sources screen) for passages relevant to a query. Use this when a question is about what the product does, how it works, pricing, or anything else better answered from the site's own declared content than from session/analytics data. Each result carries its source URL — cite it when you use the content.

search_site_knowledge

Paginated session recordings of users who dropped at (or converted through) a funnel step, with replay URLs — the "show me who got stuck at step 2" tool. Run get_funnel_analysis first to see where the drop-off is.

get_funnel_sessions

Show which FullSession account is connected: the signed-in user's email, customer ID and accessible site IDs. Use when the user asks which account or sites they're connected with.

whoami

MUTATES DATA: changes a funnel's name, base audience, steps or chart settings. Only the fields you pass change; everything else keeps its current value (to rename, pass just funnelId and funnelName). Changing steps replaces all of them and reprocesses the funnel's data. A funnel can't be edited while it is still processing (a few minutes after creating it or changing its steps). Confirm the change with the user before calling.

update_funnel

MUTATES DATA: changes a segment's title, description or filters. Only the fields you pass change; everything else keeps its current value (to rename, pass just segmentId and title). Changing filters replaces all of them; build new filters with generate_segment_from_prompt, not by hand — this tool runs the real filter → query conversion before saving and rejects filters that don't actually resolve to anything. Confirm the change with the user before calling.

update_segment

MUTATES DATA: changes one or more fields of a saved heatmap view (title, page, device, segment, time range, funnel scope). Unlike segments/funnels this is a partial patch — omitted fields are left as-is. Confirm the change with the user before calling.

update_heatmap