Skip to main content
Glama

omniseek_transcribe

Transcribe the spoken content of any video, podcast, or audio URL into text using local ASR. Select a time slice or full episode, auto-detect language, and optionally identify speakers for interviews or multi-host shows.

Instructions

Transcribe the SPOKEN content of a video / podcast / audio URL via local SenseVoice ASR (free, keyless, private, cached forever; chosen over Whisper after a real-audio benchmark — Whisper hallucinates on Chinese podcast intros). For the 干货-in-audio case where the substance is in the audio, not any text: bilibili videos (论文精读 / 方法论 / 读博 / 求职 talks), 小宇宙 podcasts, or any direct audio-file URL. (youtube already returns its captions via omniseek_read — no ASR needed; use that instead.)

Fully-qualified MCP name: mcp__omniseek__omniseek_transcribe (server name is omniseek; there is no omniseek-eye server).

THE LONG-EPISODE PATTERN: do NOT transcribe a 2-3h episode whole (30k+ chars nobody reads). Pull the chapter timestamps from the episode's shownotes (小宇宙 episode pages list them; use omniseek_search(query, sources=["xiaoyuzhou"], raw=True, full=True) / omniseek_read first), judge WHICH chapter matters, then transcribe just that slice: start="1:02:30", duration="12:00". Accepts seconds ("3750") or MM:SS / HH:MM:SS. Slices are also fast to start — on direct/enclosure audio only the slice region is downloaded. The flat transcript covers [start, start+duration] of the source audio. Pass segments=True to ALSO get a per-VAD-segment segments: [{start,end,text}] list (seconds) so a no-shownote episode becomes navigable / time-citable (the flat transcript is unchanged; segments costs an extra VAD + a batched re-transcribe pass, so request it only when you need the offsets).

Whole-item transcription remains right for short/dense items (a 10-min talk, a keynote clip); it is SLOW on first call for a long item, then cached forever. Reach for it deliberately on ONE item you've judged worth it, never as part of a broad sweep.

language: "" auto-detects; set "zh" / "en" to skip detection and sharpen accuracy when you already know the language.

diarize=True answers WHO said what (interviews / 对谈 / multi-host podcasts): segments become [{start,end,text,speaker}] with per-turn speaker labels and speakers gives the distinct count. It routes through a Chinese-focused diarization pipeline (Paraformer-zh + cam++ speaker clustering), a SEPARATE and heavier pass than the flat SenseVoice path, so request it only when the speaker turns matter, and expect zh accuracy (English audio is not its target). Cannot combine with plain segments (diarize supersedes it). speaker values are cam++'s cluster indices (0,1,2,...).

speakers=N pins the diarization to N speakers (the KNOWN head-count: a 1-on-1 interview = 2, a solo talk = 1, a 3-host panel = 3). PASS IT whenever you know the count: cam++'s automatic estimate is unstable on short / noisy slices and will over- or under-split, so pinning N is what makes the turns track reality. Leave it 0 (auto) only when the count is genuinely unknown. Ignored unless diarize=True.

Returns: {url, transcript, chars, audio_seconds, asr_seconds, source, title, cached, start_seconds?, duration_seconds?, segments?, speakers?} — or {url, error, transcript:""} if no audio resolved.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
startNo
diarizeNo
durationNo
languageNo
segmentsNo
speakersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full behavioral burden, and it delivers: it discloses that the service is free/keyless/private/cached forever, that long-item first calls are SLOW, that slices download only the needed region, that diarize is a separate heavier pass, that segments and diarize are mutually exclusive, and that speaker values are cluster indices. These are exactly the non-obvious behavioral traits an agent needs to set expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long, but it is well-structured with thematic paragraphs, inline code formatting, and front-loaded purpose/alternative information. Each section earns its place by enabling correct invocation, though a few sentences (e.g., the Whisper benchmark rationale) are context rather than necessity. It is slightly verbose but not bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex 7-parameter tool with no annotations and no output schema, the description is remarkably complete. It covers all parameters, provides the full return object shape including optional fields and error case, explains interacting flags, and addresses performance characteristics. An agent can invoke this tool correctly with no further information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does comprehensively. It explains the url, start/duration formats (seconds or MM:SS/HH:MM:SS), language auto-detection and the benefit of setting it, segments as an extra VAD pass, diarize as superseding segments, and speakers as a pinning mechanism ignored unless diarize=true. Every parameter is given semantic meaning beyond its name and type.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Transcribe the SPOKEN content of a video / podcast / audio URL via local SenseVoice ASR'. It also differentiates from the sibling omniseek_read by explicitly stating that YouTube already returns captions via omniseek_read and ASR is not needed, so an agent can immediately tell which tool to use without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description is explicit about when to use the tool: bilibili videos, 小宇宙 podcasts, or direct audio-file URLs, and when not to: YouTube, which should use omniseek_read instead. It also provides a clear long-episode pattern (pull chapter timestamps, transcribe only a slice) and warns against whole-item transcription for long episodes. This is concrete, actionable routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.