The Transcriptor MCP server provides 8 video-related tools with reasonable naming following verb_noun conventions (get_*, search_*). All tools have descriptions and documented input schemas with type information and enums for constrained fields. However, output schemas are not documented anywhere in the provided code, parameter descriptions lack detail on formats/constraints, and there is no evidence of error handling patterns or recovery guidance. Tool descriptions are adequate but brief (mostly 50-150 chars, at the lower end of the 194-char baseline). The server follows a clear single-responsibility pattern per tool and uses proper HTTP transport. The main gaps are: (1) undocumented output structures that LLMs must infer, (2) missing parameter constraints (e.g., no min/max for 'seconds' in get_video_frame, no format spec for 'lang' codes), and (3) no error handling or recovery documentation visible in tool definitions.

• Document output schemas for all 8 tools. For each tool, define the response object with field names, types, and descriptions. Example: get_video_info should return {title: string, description: string, duration_seconds: number, view_count: number, upload_date: string, channel_name: string, ...}.
• Add min/max constraints to numeric parameters. E.g., 'seconds' in get_video_frame should have minimum: 0, maximum: <video_duration>. 'quality' should be minimum: 0, maximum: 100 in the JSON schema and reiterated in the description.
• Specify format for language codes. Add to parameter descriptions: 'Language code in BCP 47 format (e.g., en, es, fr, zh-CN)' and consider adding a pattern regex to the schema.
• Add error guidance to every tool description. Include a sentence like 'If the video URL is not supported, this tool will return an error listing available platforms. If subtitles are not available, it will return an empty list.'
• Clarify pagination in get_transcript. Document the cursor format, what happens when cursor is absent (returns first page?), and the structure of the paginated response (does it include next_cursor, total_count, has_more?).
• Distinguish between get_subtitles, get_raw_subtitles, and get_transcript in their descriptions. Add guidance: 'Use get_subtitles for cleaned, searchable plain text. Use get_raw_subtitles if you need SRT/VTT format for playback. Use get_transcript for full transcript with chapters and search.'
• Add per-tool error examples. For each tool, document at least 3 failure modes and the expected error response format, e.g., 'Returns {error: 'unsupported_platform', message: 'TikTok videos are not supported', available_platforms: [...]}'.

Inferred effective spec: 2025-06-18+.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry