MCP server for litmedia.ai text-to-image and image-to-video generation
Three tools with complete schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. Tool names follow verb_noun convention (generate_image, get_user_info, generate_video). Descriptions are present (avg 150 chars) but lack actionable context for LLM selection. Most parameters have descriptions, but several lack type constraints or format guidance. No documented output schemas. Error handling returns isError flag but lacks recovery guidance or categorization.
Génère une ou plusieurs images depuis un prompt texte via litmedia.ai. Retourne les URLs publiques des images générées.
Génère une vidéo (5s par défaut) à partir d'une image de référence (URL https:// ou chemin local) et d'un prompt d'animation via litmedia.ai. Coûte 20 crédits. Retourne l'URL .mp4 publique.
Retourne les crédits restants, statut VIP et modèles autorisés du compte litmedia configuré.
Output schemas not documented. Tool descriptions state what is returned (URLs, user info, video URL) but no structured schema is provided for LLM planning. LLMs cannot reliably extract fields or chain tools without knowing response structure.
Parameter 'model' in generate_image and generate_video lacks format guidance. Description says 'ID du modèle litmedia (défaut 14)' but does not specify valid range, constraints, or how to discover available models. LLMs may pass invalid IDs.
Error handling returns isError + text but does not categorize errors or provide recovery guidance. A failed API call returns raw message with no hint whether to retry, ask user, or abort. Violates recovery-guide pattern.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 64 | 2026-07-28+ | v2 |
Credentials (LITMEDIA_TOKEN, LITMEDIA_FINGERPRINT) injected via environment at startup, which is correct. However, no audit logging of tool calls. No record of who called what tool, when, or with what parameters, violates audit-trail pattern for compliance and debugging.
generate_video accepts local file paths (relative/absolute) but no validation or sanitization shown. Path traversal risk if user-controlled input reaches uploadImage(). Input must be validated against directory bounds.