Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SM_API_URLNoWhere the MCP server finds the smovie API.http://127.0.0.1:8787
SM_API_TOKENNoBearer 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
submit_videoA

Add a YouTube or TikTok URL to the download queue.

when: "now" jumps the queue, "queue" waits its turn, "schedule" starts at run_at
(ISO 8601, e.g. "2026-10-29T02:00"; no timezone = the server's local time).
max_height caps resolution (e.g. 1080). Returns the job, including its id.
purpose: "depth" (or "action") hands the finished file to Animation Studio (codex-3d), which picks up
done jobs by itself; studio carries its fields: id, name, rights, and optionally window [start, end]
in seconds and scene (then a depth reference is made for that window).
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 8 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness5/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues