Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FFMPEG_BINNoPath or command name for FFmpeg (defaults to ffmpeg if not set)
FFPROBE_BINNoPath or command name for FFprobe (defaults to ffprobe if not set)
AERENDER_BINNoPath to Adobe After Effects aerender executable
COMFY_LOCAL_URLYesURL of the ComfyUI server (e.g., http://127.0.0.1:8188)
VIDEO_FACTORY_ROOTYesAbsolute path to the workspace directory where all video production files are stored

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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
comfy_submit_workflowB

Submit a ComfyUI workflow JSON to local or cloud ComfyUI /prompt endpoint.

comfy_get_historyC

Read ComfyUI generation history by prompt id.

media_probeB

Use ffprobe to inspect a video/audio/image file under VIDEO_FACTORY_ROOT.

ffmpeg_transcodeC

Transcode or resize a video using safe preset options.

ae_generate_jsxB

Generate an ExtendScript JSX file that opens an AE template and replaces footage/text layers.

ae_render_templateB

Invoke aerender to render an AE comp. Use dryRun first to verify command.

pipeline_create_jobC

Create a structured job folder and manifest for an AI video production pipeline.

review_video_packageC

Basic placeholder review for video metadata. Replace with real moderation APIs later.

platform_prepare_packageC

Generate publishing metadata for different short video platforms.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 9 tools

Disambiguation5/5

Each tool clearly targets a distinct domain: AE scripts vs rendering, ComfyUI submission vs history, media probing vs transcoding, pipeline job creation, platform packaging, and review. No overlapping purposes.

Naming Consistency4/5

Names mostly follow a consistent verb_noun pattern with domain prefixes (ae_, comfy_, ffmpeg_, media_, pipeline_, platform_, review_). The only minor inconsistency is 'media_probe' which reverses the order (noun_verb) compared to others like 'ffmpeg_transcode'.

Tool Count5/5

9 tools cover the key operations for a video factory: AE template generation and rendering, ComfyUI workflow management, media processing, pipeline orchestration, and platform publishing. The count is well-scoped without unnecessary bloat.

Completeness4/5

Covers essential workflows: AE template manipulation, ComfyUI interaction, media transcoding/probing, pipeline job creation, and platform packaging. Minor gap: the review tool is a placeholder, and there is no explicit tool for asset management or user input validation, but core functionality is present.

Maintenance

ActivityInactive
ResponsivenessNo issues