HappyScribe

Check an export that export_transcription reported as still processing, and get its link.

get_export_status

Get the folder hierarchy with transcription counts. Shows accessible folders organized by location (Team, Private, Shared with me). USE THIS when list_transcriptions returns more results than you can effectively browse and you need to understand how transcriptions are organized. Then use list_transcriptions with folder_path to browse specific folders.

get_folder_hierarchy

Get a glossary with all its terms. Returns the full term list including source text, translations, and context notes.

get_glossary

Fetch one HappyScribe helpdesk article by ID and return its title, full body, and URL. Use this when you already know the article ID. To find an article by keyword, use search_helpdesk first.

get_helpdesk_article

Get detailed diagnostic information about why a meeting was or wasn't recorded. Use this to debug failed recordings, understand bot behavior, and troubleshoot calendar integration issues. Provides information about: calendar event details, notetaker meeting status, bot status, recording configuration, and reasons why the bot didn't join or recording failed.

get_meeting_diagnostics

Get detailed profile for a specific person including their company, transcription statistics, and recent transcriptions.

get_person

Get the full details of a summary template by ID (for user/workspace templates) or slug (for system templates). Returns the name, markdown body, sections, meeting context, and visibility.

get_summary_template

Read a transcription yourself (text, summary or metadata) to answer questions, summarize or quote it. show_transcript displays a transcript to the user as a card with a player.

get_transcription

Check the progress of a transcription, by the order_uuid from create_transcription or by a transcription_id. Returns one status (importing, analyzing, transcribing, needs_credits, waiting_for_payment, done or failed) and the next step. While it runs, poll_after_seconds says when to check again. HappyScribe sends no notification in the chat when it finishes: the transcript is ready once this reports done, and the user can ask for a new check anytime.

get_transcription_status

Get detailed information about multiple transcriptions at once. Use this after listing transcriptions to get full content/summaries for multiple files efficiently.

get_transcriptions

Part of the HappyScribe upload box, which calls it itself. Attached files go to create_transcription in media_file.

get_upload_url

Extract visual frames (screenshots) from a video recording at specific timestamps. Use this when the conversation references something visual — a screen share, presentation, diagram, or UI — and you need to see what was on screen. Returns the frames as images. Only works for video recordings (meetings, screen recordings); audio-only files have no frames.

get_video_frames

Get information about the current workspace this connection has access to

get_workspace

List calendar events (scheduled meetings) with their recording status. Use this to see what meetings are scheduled, which will be recorded, and prepare for upcoming meetings. Supports date filtering to find meetings in specific time ranges (past, present, or future). Can filter by series_ids to get all instances of recurring meeting series. The current year is 2026.

list_calendar_events

Browse and search companies in the knowledge graph. Returns companies with their people count and transcription statistics.

list_companies

List glossaries in the workspace. Glossaries define terminology that should be used consistently in transcriptions and translations — preferred spellings, proper nouns, domain-specific terms, etc.

list_glossaries

Browse and search the people from recordings in the user's connected HappyScribe workspace. Returns only contacts the user can see, with their company and how many recordings they appear in.

list_people

List files already read this month and show remaining quota. Some plans have a monthly limit on how many unique files can be read with display_mode: "full_text" — once a file has been read, re-reading it is always free. Summaries and metadata are also always free.

list_read_files

List meeting summary templates available in the workspace. Returns your private templates, shared workspace templates created by teammates, and built-in system templates. Templates define the structure and sections of AI-generated meeting summaries.

list_summary_templates

List transcriptions accessible to the user with optional filtering. Returns results ordered by creation date (newest first). A good starting point to see recent transcriptions. When the user asks about their own transcriptions (e.g. "my files", "my meetings", "meetings I was in", "calls I had this week"), pass scope: 'mine' — it restricts results to files the user owns, participated in (as speaker or calendar attendee), or that were directly shared with them, mirroring the dashboard "My files" view. Without it, results include every file the user can access via folder permissions. If there are too many results to browse, get_folder_hierarchy shows the folder structure so you can narrow down with folder_path. Supports filtering by folder (folder_path), location, date range, person, company, and pagination. When filtering by person or company, list_people or list_companies can help find the exact name first; person_email is the most reliable filter.

list_transcriptions

Listen to a specific segment of a transcription's audio with an audio model and answer a question about it. Use this when you need to hear what actually happened in the audio — tone of voice, background noise, overlapping speakers, pronunciation, music, non-verbal cues, or anything the transcript text cannot capture. Requires start_time and end_time in seconds (max 5 minutes per clip). Use timestamps from the transcription content to target the segment of interest.

listen_to_audio

Move one or more transcriptions to a different folder in the same organization. Accepts up to 50 transcription IDs per call. Use list_transcriptions or get_folder_hierarchy to look up the destination folder ID first. Cross-organization moves are not supported. Authorization is checked per transcription and on the destination folder; if any check fails, no transcriptions are moved.

move_transcriptions

Reassign speakers for one or more time ranges in a transcription. The server splits affected paragraphs at word boundaries and assigns the given speaker label to all words in each range. Adjacent paragraphs with the same speaker are merged automatically. Use this to fix diarization errors where paragraphs contain speech from multiple people. Returns the resulting speaker timeline so you can verify the changes.

reassign_speakers

Regenerate the meeting summary for a transcription. Optionally specify a template to use — otherwise the existing template (or the default from the resolution chain) is used. The summary is generated asynchronously; use get_transcription to check the result.

regenerate_summary

Rename a folder.

rename_folder

Rename one or more speakers in a transcription. Pass a mapping of current speaker label -> new speaker label, e.g. { "Speaker 1": "Alice", "Speaker 2": "Bob" }. All paragraphs whose speaker matches a key are updated. Match is exact (case-sensitive). Use get_transcription first to see the current speaker labels.

rename_speakers

Rename a single transcription.

rename_transcription

Apply several find-and-replace fixes to one transcription in a single new version. Several fixes in one call make one version, where replace_text_in_transcript makes one per fix. Pairs run in order, each on the result of the ones before (so a later find can match text an earlier replace produced). Matching is exact and case-sensitive. The optional time window applies to every pair. Pairs that match nothing are reported and skipped.

replace_text_batch

Find and replace exact text in a transcription. Replaces every occurrence of `find` with `replace` across all paragraphs. Optionally constrain to a time window with `from_seconds` and `to_seconds` — only occurrences whose word-level timestamps intersect that window are replaced. Use this to fix consistent typos, names, or product mentions. One call fixes every occurrence of a phrase and saves a new version, so one call per distinct phrase covers a file. For speaker label changes, use rename_speakers instead.

replace_text_in_transcript

Records a request that no available tool can handle, so the HappyScribe team learns what to build next. The capability is described in general terms (for example "translate a transcript into German" or "send the summary to Slack"), without names, emails or other personal details. It is not for requests an available tool covers, nor for errors that already name a next step (a missing summary, a file still processing, no minutes left). One call per request is enough. It does not add new tools.

request_missing_capability

Re-runs automatic transcription (ASR) on the existing media of a transcription already in the workspace, replacing the current transcript in place (the transcription keeps its ID). This replaces everything: transcript text, speaker diarization, and speaker labels. Any edits the user made — including renamed speakers — will be lost (recoverable from version history inside the editor). There is no way to reprocess only one aspect; retranscription always re-runs the full pipeline. Use this to fix a file that was transcribed in the wrong language, or to re-process it after its settings changed. Only finished automatic transcriptions with their media still available can be retranscribed. It overwrites the user's edits and may use credits, so it needs the user's agreement first. It does not help a failed or slow file: a running file is still processing, and a failed one needs a new create_transcription. It runs in the background; its reply says how to follow it. To apply glossaries, pass glossary_ids: they are added to the ones the file already uses.

retranscribe

Search HappyScribe helpdesk articles to answer questions about product features, policies, and how-to guides. Use this when the user asks about: how HappyScribe works, product documentation, feature explanations, pricing details, data policies (e.g., "how long are files stored?", "is my data used for training?"), account settings, troubleshooting, or any question that might be answered in help documentation. This searches published help center articles and returns relevant excerpts with links to the full articles.

search_helpdesk

Search for exact text/keywords within transcription content (like grep). Use this to find specific names, product names, or exact phrases. For browsing by topic, date, or category, use get_folder_hierarchy + list_transcriptions instead.

search_transcriptions

Configure which summary template to use for future meetings. With scope "meeting": sets the template on a calendar event (and all upcoming instances if recurring). With scope "default": sets the template as your personal default for all future meetings.

set_meeting_template

Share a transcription: invite people by email with view or edit rights, and/or turn the public link on (view only or editable) or off. Invited people get an email from HappyScribe, so it fits an explicit request to share, with the exact emails and view/edit rights confirmed by the user. A public link lets anyone with it open the file, so it fits an explicit request for one. Leaving public_link out keeps the link as it is. Returns the link to share.

share_transcription

Show a transcript to the user as a card in the chat, with an audio player and the first paragraphs, which expand in place. It fits a user who wants to see, open, read or listen to a finished transcript, including right after an upload finishes. It works for files that get_transcription_status reports as done. One card shows one transcript, so several files take one call each. get_transcription returns the text for you to read.

show_transcript

Unlock a transcription that get_transcription_status reported as needs_credits, spending the workspace credits it costs so it continues. It spends the user's credits, so it needs the user's explicit agreement for this file. If the workspace still cannot afford it, the user can upgrade in their HappyScribe account; adding minutes does not resume the file by itself, it still has to be unlocked.

unlock_transcription

Edit a glossary: rename it, change its languages or default status, and add, edit or remove terms. Terms to edit or remove are matched by their current text (case-insensitive). Use get_glossary first to see the current terms.

update_glossary

Update an existing summary template (name, body, meeting_context, or visibility). Only the template creator can edit it. Omitted fields are left unchanged. The body is markdown where each ## heading becomes a section in the generated summary. Visibility is "private" (only you) or "workspace" (all team members).

update_summary_template

Show an upload box in the chat where the user can drop or pick one or more audio or video files from their device, on desktop or mobile. It fits any request to upload, send or transcribe a file that has not been attached in a form you can pass yourself, including a plain "I want to upload a file", and attachments in clients that give no file access. Documents and images are out of scope. The box uploads each file, starts its transcription and shows progress itself, so its files need no create_transcription call. Once it shows "Uploaded", the user can ask anytime whether the transcript is ready.

show_upload_box