Video Jungle MCP Server for Adding, Analysing, Searching, and Editing Videos
Video Editor MCP has 11 tools but suffers from critical gaps in definition quality. Only 2 tools have visible input schemas (create-video-bar-chart-from-two-axis-data and create-video-line-chart-from-two-axis-data), while the remaining 9 tools have NO visible schema definitions in the source code provided. No tool descriptions are visible in the source excerpt. Naming is reasonable (verb-noun format: add-video, search-local-videos, etc.) but without schemas and descriptions, the tools are not suitable for production LLM consumption. The code shows tool registration as a list of strings, not as explicit tool definitions with descriptions and input schemas.
Missing tool descriptions: 11/11 tools have no visible descriptions. LLMs cannot determine when or why to select these tools without descriptions.
Missing input schemas: 9/11 tools have no visible input schema definitions. Only the two chart-creation tools show schema structure. Tools cannot be reliably invoked by LLMs without schemas.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 32 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 43 | - | v1 |
Parameter descriptions missing: The two visible chart tools have parameter descriptions (e.g., 'Categories for x-axis'), but no parameter type constraints or validation guidance. No indication of valid ranges, formats, or required vs optional parameters.
Ambiguous naming with 'and' patterns: Tool 'create-video-bar-chart-from-two-axis-data' bundles axis data creation with chart generation. Should separate axis preparation from visualization.
No output schemas documented: Unclear what these tools return. create-video-bar-chart-from-two-axis-data returns chart file path? Chart object? URL? LLMs cannot chain these tools without knowing output structure.
No error handling guidance: No indication of failure modes, recoverable vs fatal errors, or what the LLM should do if a tool call fails. Error responses will likely be raw exceptions.
Destructive operations without confirmation: Tools like 'add-video', 'generate-edit-from-videos', 'create-videojungle-project', and 'update-video-edit' modify state but have no visible dry-run or confirmation pattern to prevent accidental changes.
API key exposure risk: VJ_API_KEY is loaded from environment and passed to ApiClient, but there is no indication in tool definitions that this secret is properly injected server-side and not exposed as a parameter.
No pagination documented: search-local-videos and search-remote-videos likely return large result sets but no visible limit, offset, page_size, or next_cursor parameters in schemas.