MCP Server for All-in-One Transcription - YouTube, Audio, Video + Translation, Summarization, Chapters, Subtitles, Batch
Scoring was not performed
Missing output schema documentation for all tools. LLMs cannot infer what fields responses contain, preventing proper downstream tool chaining and forcing exploratory calls.
Ambiguous parameter names: 'vdo_info' uses shorthand 'vdo' instead of 'video' (consistency issue). Parameters like 'style' in summarize_transcript and 'tone' in generate_blog_post lack enum constraints in visible schema.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 16 | <=2025-11-25 | v2 |
| 2026-03-09 | D | 53 | - | v1 |
No error handling or recovery guidance in descriptions. Tools that download/process external files provide no guidance on handling network failures, file format errors, or timeout scenarios.
Missing idempotency contracts. Tools like batch_transcribe and transcribe_folder lack documentation on whether repeating with same inputs produces identical outputs or causes side effects (e.g. file overwrites, re-uploads).
Tool composition guidance missing. LLMs cannot infer the logical workflow: should they call youtube_to_text → transcribe_video → summarize_transcript → generate_blog_post? Or are some tools alternatives? No dependency hints provided.
Parameter descriptions lack constraint documentation. 'lang' parameters accept language codes but provide no list of valid codes or format (e.g., 'en', 'th', 'ja'). 'model_size' enum values listed in description but not formalized in schema.
Dual-input parameter handling (file_path vs url) lacks mutual exclusivity documentation. For audio_info, vdo_info, transcribe_audio, transcribe_video: unclear if both can be provided, what happens if only one is null, or which takes precedence.