SalesEQ

Fetch a small JPEG frame from a meeting video around a specific timestamp. Use this when the user asks to visually inspect what was happening at a known moment, usually after search_meetings returns a chunk_start_seconds or get_transcript narrows the relevant time range. The timestamp must be within the meeting's duration (duration_seconds from list_meetings). Choose max_width by need: the 320 default (~80 vision tokens) shows what's on screen; 640 (~300) makes headers readable; 1280 (~1,200) makes most on-screen text readable, and higher widths add token cost without adding detail. Frames are extracted on demand from the source video; audio-only, transcript-only, and meetings without video assets cannot return images. The response includes structured metadata and, when the JPEG is small enough, inline image/jpeg content.

get_meeting_frame

Get the AI-generated markdown summary of a meeting — far cheaper than reading the whole transcript. Use this first for questions like 'what was this call about' or 'what happened in my last meeting'; use get_transcript only when you need exact wording or the summary is unavailable. The summary is null when it hasn't been generated, most often because no speech was detected. Before falling back to get_transcript, check the meeting's has_speech flag (returned by list_meetings): when has_speech is false there is no meaningful transcript either, so report that the meeting had no speech instead of fetching it. For questions spanning several meetings (e.g. 'summarize my week'), call list_meetings for recent meeting IDs, then fetch summaries in parallel if the client supports parallel tool calls.

get_meeting_summary

Fetch the transcript for a meeting. Returns transcript text with speaker names, timestamps, and dialogue. Use start_seconds and end_seconds to request a specific time range — this avoids loading the entire transcript for long meetings. For example, to preview the first minute, use start_seconds=0, end_seconds=60. To continue reading, use start_seconds=60, end_seconds=120. Omit both to get the full transcript. All parameters here are SECONDS: search_meetings matches include chunk_start_seconds / chunk_end_seconds that can be passed here directly, while chunk_start_ms is milliseconds and must be divided by 1000 first. Pad the window around a search match (e.g. 60s each way) to read the surrounding context. The list_meetings tool returns duration_seconds for each meeting, which tells you the total meeting length. For 'what was this call about' questions, get_meeting_summary is much cheaper than reading the transcript. Some meetings are transcript-only (e.g. data backfills from other providers) and may not have real timestamps — in that case, timestamps are estimated at approximately 150 words per minute. When verifying multiple search_meetings candidates, fetch transcripts or time ranges for multiple candidate meetings in parallel if the client supports parallel tool calls.

get_transcript

Get lightweight organization context for the caller: org id/name, the current user's member record, and matching org members with user IDs, names, emails, roles, and membership status. Use this when you need to resolve a teammate's name or email to a SalesEQ user_id before calling other tools. For example, to search Austin's recorded calls, first call get_org_context with member_query='Austin', then call search_meetings with creator_id set to Austin's user_id. Use member_limit and member_offset for simple member pagination (default limit 50, max 200). This tool does not return meetings, transcripts, groups, or permission graphs.

get_org_context

List meetings the user can access, most recent first by default. `scope` is required: use `scope: 'mine'` for only meetings the user recorded or uploaded, or `scope: 'all_viewable'` for every accessible meeting. Results include each meeting's title, participants, duration, platform, creator, and whether the current user created it. Use this to find a meeting ID, then call get_meeting_summary for a quick overview or get_transcript to read the transcript. Use `creator_id` with `scope: 'all_viewable'` after get_org_context resolves a teammate's exact SalesEQ user ID. Do not use creator names or emails in creator_id; use get_org_context first. Use `meeting_participant` for a partial participant name/email match, whether or not they spoke. Use `meeting_speaker` when the person must have spoken at least one word. There is no topic search here; use search_meetings for transcript/topic search. Use `sort_by` / `sort_order` to scan by recency or duration, `has_speech` to include/exclude recordings with no detected speech, and `min_duration` / `max_duration` to skip very short test recordings. When `participants[].name` is null (participant identification isn't always populated), use `participants[].spoke` and `word_count` to distinguish speakers from detected silent attendees. To inspect the start of an unnamed-speaker meeting, call get_transcript with `start_seconds: 0, end_seconds: 90` — people typically introduce themselves at the start of a call.

list_meetings

Transcript search across the user's calls. This queries a dedicated TopK search database containing speaker-prefixed transcript chunks, vectorized roughly like `John Smith: I can make the call.\nJames Doe: Great, let's follow up tomorrow.` The speaker names and spoken words are both in the searchable text. Use this first when the user asks to find meetings 'about X', 'where we discussed Y', or 'that mentioned Z'. It ranks meetings by transcript relevance and returns each meeting's best-matching snippets with playback offsets (chunk_start_ms) and a relevance score. Only meetings the user can view are returned, so results can be fewer than top_k after authorization and stale-index filtering. Default mode is hybrid: ColBERT-style late-interaction semantic ranking with a 1.3x lexical boost. Use mode 'semantic' for pure semantic ranking, or 'bm25' for exact terms/names/IDs. Available filters include scope, creator_id, meeting_id, chunk_speaker, meeting_speaker, meeting_participant, started_after, started_before, duration bounds, speaker/participant-count bounds, platform, is_audio_only, and is_transcript_only. Name filters accept one name or a list of names with OR semantics. The default name match mode is partial, case-insensitive; use regex only for deliberate name patterns. chunk_speaker applies to the returned chunk; meeting_speaker applies to resolved speakers anywhere in the meeting; meeting_participant applies to resolved meeting participants whether or not they spoke. For broader fuzzy person search, include the name in query text too. Use get_org_context to resolve a teammate's name/email to creator_id when the user asks for meetings recorded by a specific rep. If useful, run multiple searches in parallel for distinct ideas from the user's request, with different phrasings, modes, or filters, then compare results. Search is often paired with get_transcript: use the returned meeting_id to read the full meeting or a focused time range to verify the broader context. Each match includes chunk_start_seconds / chunk_end_seconds, which are already converted to seconds for get_transcript — chunk_start_ms and chunk_end_ms are milliseconds (playback offsets), so never pass those to get_transcript without dividing by 1000.

search_meetings