GetTranscribe

@GetTranscribe list my recent transcriptions from the last week and summarize the topics covered across all of them.

Found 7 transcriptions from the past week. Topics include: three customer onboarding calls discussing feature requests for mobile notifications and SSO integration; two internal standups covering sprint planning and a production incident post-mortem; one product demo walkthrough of the new dashboard redesign; and one recorded webinar on API best practices. Most conversations centered on the Q1 roadmap and customer feedback loops.

This example shows the MCP's list-and-retrieve workflow paired with AI synthesis. The MCP returns lightweight metadata (title, date, folder) for each transcription; the AI must call Get Transcription for each item to access full text, which can trigger multiple API round-trips. Useful for cross-call pattern detection, but be mindful of rate limits when processing large result sets.

@GetTranscribe create a transcription job for this YouTube video: https://youtube.com/watch?v=dQw4w9WgXcQ and let me know when it's ready.

Transcription job created successfully. Job ID: `job_8x3k9mz`. Status: processing. Estimated completion: 3-5 minutes for a 4:12 video. This operation will consume approximately 5 minutes of transcription credits from your account balance (current balance: 847 minutes remaining). I'll need you to check back or use Get Transcription Job to poll for completion—this MCP does not support webhooks or push notifications.

Demonstrates the async job workflow for paid transcription. The MCP queues the job but does not wait for completion; you must poll Get Transcription Job or return later. Be aware this consumes account credits immediately upon submission, even if the job ultimately fails. Best for batch processing or workflows where you can afford the wait time.

@GetTranscribe check my account usage and warn me if I'm close to running out of transcription credits this month.

Your GetTranscribe account (Plan: Professional) shows 847 minutes of transcription credits remaining out of your 1,000-minute monthly allowance. You've used 153 minutes so far this billing cycle, which resets in 18 days. At your current usage rate (~8.5 minutes/day), you're on track to consume roughly 1,000 minutes total—right at your limit. Consider upgrading or rationing jobs if you have large transcription needs before the reset.

Shows the Get Current Account tool paired with AI-driven budget analysis. This is a read-only check with no side effects, making it safe to run frequently. Useful for proactive monitoring in workflows that queue many transcription jobs. Note that usage data reflects the account state at call time and may lag slightly behind real-time job submissions.

When GetTranscribe fits weekly user-research cadence

A 5-person product team runs 8-12 customer interviews per sprint and needs transcripts in Switchy for synthesis. GetTranscribe wins here because the async job model matches the workflow: queue recordings after each call, poll status in a shared channel, then pull full transcripts with timing data when synthesis starts. The folder structure keeps interviews organized by sprint or theme without manual tagging. The trade-off is cost visibility—each Create Transcription Job consumes credits, so teams burning through 40+ hours of audio per month should check their plan limits with Get Current Account before scaling. If your team already has enterprise Zoom or Teams transcription, you probably don't need this. But if you're stitching together Loom links, Riverside recordings, and ad-hoc Meets calls, GetTranscribe gives you one queue to rule them all.

Why GetTranscribe beats manual notes at seed stage

A two-founder SaaS team closes 15-20 discovery calls per month and wants searchable transcripts without hiring a VA. GetTranscribe is the right call when you need async processing—drop the call URL, get a job ID, check back in Switchy when it's done. The List Transcription Jobs filter by status means you can batch-review finished calls during Friday retros instead of babysitting each upload. The folder system is overkill at this scale, but the word-level timing in Get Transcription helps you jump to objection-handling moments or feature requests when writing follow-ups. The ceiling is around 30 calls per month—past that, the per-job polling gets tedious and you want a webhook-driven integration. If you're doing same-day call prep, the async delay (usually 5-15 minutes) might be too slow; live transcription wins there.

When GetTranscribe handles multi-episode transcript pipelines

A 3-person podcast team ships two episodes per week and needs transcripts for show notes, SEO, and sponsor reads. GetTranscribe fits because the folder structure mirrors their season-and-episode taxonomy, and the List Transcriptions filter lets them pull all Season 3 transcripts in one Switchy query when writing the finale recap. The async job queue handles batch uploads—drop 4 episode URLs on Monday, poll status Tuesday, pull full text with segments for the editor by Wednesday. The gotcha is timing granularity: if you need speaker diarization or paragraph-level structure for blog posts, you'll do that cleanup in Switchy after retrieval. GetTranscribe gives you raw text and word timing, not formatted show notes. If your episodes run over 90 minutes or you're publishing daily, check your account balance with Get Current Account before queuing a month's worth of jobs.