Transcriptor

transcript_create

Start a transcription job for a local media file or supported URL and get a job ID right away; poll status and fetch partial results as processing continues.

Instructions

Start a transcription job and return its id immediately.

source is either an absolute local path (~ is expanded) or a URL — YouTube, Instagram, TikTok, X, Vimeo, Reddit and anything else yt-dlp supports, plus direct media URLs. Relative paths are refused, and a playlist or channel URL is refused as ambiguous: pass one video.

The call never waits for work. Poll transcript_status, and read partial output with transcript_get while it runs.

captions decides whether to use a platform's existing subtitles instead of transcribing: manual_only (default) takes human-written captions when present, which are usually better than Whisper; prefer also accepts auto-generated ones, which are usually worse; never always transcribes. The result reports origin so you know which you got.

language is an ISO code to force; omit it for automatic detection. force bypasses the cache and re-transcribes.

Sources longer than four hours are refused. Login-walled, private, members-only or age-restricted URLs fail with auth_required — set TRANSCRIPTOR_COOKIES_FROM_BROWSER (chrome, safari, firefox, brave) or TRANSCRIPTOR_COOKIES_FILE in the server's .env and retry.

Input Schema

TableJSON Schema

Name	Required	Default
`force`	No
`source`	Yes
`captions`	No	manual_only
`language`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 15, 2026

TDQS

A5/5.0

Behavior5/5

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

No annotations are provided, so the description carries the full burden and does so well: it discloses the async/non-blocking behavior, the cache-bypass semantics of force, the 4-hour source limit, the auth_required failure mode and the exact env vars (TRANSCRIPTOR_COOKIES_FROM_BROWSER/FILE) needed to work around it. This is far more than the schema conveys.

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

Conciseness5/5

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

Though multi-paragraph, it is front-loaded with the core behavior first and then parameter semantics, and every sentence adds operational value that the 0%-covered schema and absent annotations leave unstated. No filler or restatement of the name.

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?

An output schema exists, so the description needn't detail return shape, yet it still notes that the result reports origin. Combined with the failure modes, limits, follow-up calls, and per-parameter semantics, an agent has everything needed to invoke this correctly.

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 fully compensate, and it does: source (absolute path/expanded ~ vs URL, yt-dlp coverage, direct media URLs), captions (manual_only/prefer/never tradeoffs and the reported origin), language (ISO code, omit for auto-detect), and force (bypasses cache) are all explained with meaning beyond the bare types.

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?

States a precise verb+resource and its synchronous contract: 'Start a transcription job and return its id immediately.' It also implicitly distinguishes itself from the polling/read siblings it names (transcript_status, transcript_get), so an agent knows this is the initiation call, not the retrieval call.

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?

Explicitly tells the agent how to proceed after calling ('Poll transcript_status, and read partial output with transcript_get while it runs'), names the alternatives for the follow-up work, and states refusal conditions (relative paths, playlists/channels, >4h sources) with the retry path for auth-walled URLs.

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

Deploy Server