Short drama and manga generation service with Seedance 2.5 video generation and Volcengine drama composition
Server defines 13 tools with basic schemas and descriptions, but quality is inconsistent. Most tools have descriptions (10-100 chars, below the 50-200 char baseline for LLM optimization), and input schemas are present but minimal. Critical gaps: no output schemas documented, no error handling guidance, no parameter descriptions for most inputs, and no tool annotations (readOnlyHint/destructiveHint). Tools like 'availability' and 'projects' have empty input schemas with no descriptions. The 'create' tool has the most complete schema, but even it lacks output documentation. No evidence of idempotency, pagination, or recovery guidance. Naming is verb-based but generic (e.g., 'refresh', 'submit', 'reconcile' lack clarity on what they return or when to use them vs. similar tools).
Admin-initiated refresh of task progress from upstream (admin only)
Get availability status of drama and video generation services with costs
Create a new short drama project with script, visual style, and aspect ratio
Get details of a specific short drama project including all tasks
List all short drama projects for the authenticated user
Reconcile a task with upstream task ID or confirm rejection for refund (admin only)
Query upstream task progress and update local task status
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., project_id, task_id, status). Agents must guess response structure.
Empty input schemas for 'availability', 'projects', 'settings', 'tasks'. These tools accept no parameters but lack descriptions explaining what they return or when to call them.
Parameter descriptions missing or minimal. 'id' appears in 6 tools but only 'project' and 'script' describe it as 'Project UUID'. Others lack context. 'stage' enum in 'submit' has no description of what each stage does or when to use them.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 51 | 2026-07-28+ | v2 |
Delete a short drama project and all associated local records
Update media studio configuration including service credentials and costs (admin only)
Download project script as plain text with temporary token authentication
Get media studio configuration and enabled features (admin only)
Submit a project stage for processing (script analysis, image generation, video generation, or composition)
List recent short drama tasks with status and error information (admin only)
No error handling guidance. Tools like 'remove' (destructive) and 'submit' (async processing) lack recovery hints. No indication of retryable vs. fatal errors, or what to do if a task fails.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Agents cannot distinguish safe reads from destructive writes. 'remove' should be marked destructive; 'refresh' should indicate idempotency.