smovie-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SM_API_URL | No | Where the MCP server finds the smovie API. | http://127.0.0.1:8787 |
| SM_API_TOKEN | No | Bearer token for the API, needed if the service was started with SM_API_TOKEN set. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| submit_videoA | Add a YouTube or TikTok URL to the download queue. |
| list_jobsA | List recent jobs, newest first. status filters by comma-separated states: scheduled, queued, downloading, done, failed, canceled. |
| get_jobC | Get one job: status, progress %, speed, title, filename, error. |
| wait_for_jobC | Wait until a job is done, failed or canceled (or the timeout passes) and return it. |
| save_videoB | Copy a finished job's file from the service to a local folder. Returns the saved path. |
| cancel_jobC | Cancel a scheduled, queued or running job. |
| retry_jobA | Put a failed or canceled job back in the queue. |
| delete_jobB | Remove a job from the list, and its file from the server unless delete_file is false. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct role across the job lifecycle: submit, inspect, list, wait, save, cancel, retry, and delete. The nearest pair, get_job and wait_for_job, is differentiated by wait_for_job blocking until a terminal state or timeout.
All eight tools follow a consistent snake_case verb_noun pattern (get_job, submit_video, list_jobs, wait_for_job, save_video, cancel_job, retry_job, delete_job). No mixed casing or inconsistent verb styles appear.
Eight tools is well-scoped for a video download queue service, covering submission, monitoring, waiting, file retrieval, and lifecycle management without bloat. Each tool earns its place in the workflow.
The surface covers the full job lifecycle: create/submit, get, list, wait, save finished files, cancel, retry, and delete. Scheduling and Animation Studio handoff are handled through submit_video, leaving no obvious dead ends for the stated purpose.