Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CLIPUGC_API_KEYNoYour ClipUGC API key from the dashboard (Dashboard, API Keys). Without it the server starts but every tool answers with an auth error.
CLIPUGC_API_BASE_URLNoOptional. API base URL, defaults to https://clipugc.com/api/v1.

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
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_charactersA

List ClipUGC AI characters (AI influencers). Same as clipugc characters list. scope "mine" (default) lists the authenticated user's own characters, "discover" the public feed, "feed" own characters first then public ones. Returns items with id, display_name, age, gender, is_public, status, plus pagination. Costs no credits.

create_characterA

Create a new AI character from a plain-text description. Same as clipugc characters create. The server extracts the appearance DNA and generates the first look automatically (2 credits; confirm with get_credits). Be specific: nationality, age, hair, eyes, face shape, skin, style, and a realism anchor such as "natural skin texture, not airbrushed". Characters are public by default; set private=true to opt out. make_video=true also stages the first clip (extra clip cost). Returns the character with first_look_id. Looks generate in the background. Poll list_images with the same character id every 5 to 10 seconds until each new look has status "completed" (or "failed"), then pass the look id to create_clip. Advanced: pass name (2-120 chars) plus optional age, gender, dna_json instead of description for a structured create.

generate_imageA

Generate one or more new looks (reference images) of an existing character. Same as clipugc images generate. Every look is generated from the character's base image, so the face stays the same person: only describe the new setting, outfit and light in scene, never the person again. Costs 2 credits per shot (confirm with get_credits). Returns the created image ids. Looks generate in the background. Poll list_images with the same character id every 5 to 10 seconds until each new look has status "completed" (or "failed"), then pass the look id to create_clip.

list_imagesA

List the looks (reference images) of a character with id, status (pending, processing, completed, failed), scene_prompt and image url when ready. Same as clipugc images list --character <id>. Also the poll call for generate_image and create_character. Costs no credits.

create_clipA

Animate a character look (or your own photo) into a short video clip. Same as clipugc videos create. Costs 7 credits for 5 seconds or 13 for 10 seconds; adding scene makes it a scene-staged clip (9 at 5s, 15 at 10s). Confirm with get_credits first. Prefer a silent reaction prompt (mouth closed, no talking, an arc in beats, ambient motion): lip-sync from a still image is what makes AI video look fake. Provide exactly one of image or photo. Returns the clip id and status. Generation runs in the background. Poll get_video with {"id": , "kind": "clip"} every 5 to 10 seconds until status is "completed" or "failed", then call download_video.

create_motion_clipA

Animate a character look (or your own photo) by copying the motion of a driver video. Same as clipugc videos motion. Two engines: kling (default, 3 credits per second of driver video, reads the prompt) or wan (2 credits per second, keeps the look's own background, ignores the prompt, resolution 480p, 580p or 720p). Rounded up, capped at 30 seconds (confirm with get_credits). The driver must be mp4/mov, at most 50 MB and 30 seconds; it is uploaded first. Provide exactly one of image or photo. Returns the clip id and status. Generation runs in the background. Poll get_video with {"id": , "kind": "clip"} every 5 to 10 seconds until status is "completed" or "failed", then call download_video.

create_scene_replace_clipA

Put an AI influencer into a video the user filmed or holds the rights to: the AI influencer takes the place of the person in it, in that video's own room, light and camera, and the clip carries a visible "AI generated" label. Same as clipugc videos replace. Needs a look of an AI influencer designed in ClipUGC (not the user's own photo) and a local video file, mp4/mov, at most 50 MB and 30 seconds; it is uploaded first. Costs 3 credits per second of the video, rounded up, capped at 30 seconds (confirm with get_credits). Rendering takes several minutes. Returns the clip id and status. Generation runs in the background. Poll get_video with {"id": , "kind": "clip"} every 5 to 10 seconds until status is "completed" or "failed", then call download_video.

merge_adA

Put an app screen recording and a hook text overlay (plus optional background music) into a completed clip to make the finished UGC video for the app. Same as clipugc videos merge <clipId>. The clip must have status "completed" (check with get_video). This step is free at the time of writing; the live cost is the merge key of get_credits. Files are uploaded first. Returns merged_video_id: the finished video id, which is a different id space from the clip id. The finished video renders in the background. Poll get_video with {"id": <merged_video_id>, "kind": "finished"} every 5 to 10 seconds until status is "completed" or "failed", then call download_video with kind "finished".

get_videoA

Get the current status of a clip (kind "clip", default; same as clipugc videos status <id>) or of a finished video (kind "finished"; same as clipugc finished show <videoId>). This is the poll tool for create_clip, create_motion_clip and merge_ad. Status is pending, processing, completed or failed. A clip record also carries merge_status and merged_video_id once a finished video was made from it. Costs no credits.

download_videoA

Download a completed clip (kind "clip", default; same as clipugc videos download <id>) or a completed finished video (kind "finished"; same as clipugc finished download <videoId>) to a local mp4 file. Pass an absolute output path; missing parent directories are created. Costs no credits. Fails if the video has not completed yet.

get_creditsA

Return the authenticated user's credit balance and the live per-action credit costs (keys image, clip, clip_10s, scene_staged, motion_per_second, motion_wan_per_second, scene_replace_per_second, merge). Same as clipugc credits. Call it before any generation tool so you can tell the user the cost and stop early when the balance is too low. Costs no credits.

list_hooksA

Get AI-suggested hook texts (the short attention-grabbing line burned over a UGC video). Same as clipugc hooks suggest. Pass context describing the app for tailored hooks. Pick one (max 150 chars) and pass it as hook to merge_ad. Costs no credits.

Prompts

Interactive templates invoked by user choice

NameDescription
make_ugc_videoWalks the model through the whole ClipUGC pipeline for one video: pick or create the influencer, make the clip, add the app recording, download.
new_ai_influencerCreates a private ClipUGC AI influencer from a plain description and waits for its first photo.
hook_ideasAsks ClipUGC for hook lines (the first words on screen) for an app, then picks the strongest three.

Resources

Contextual data attached and managed by the client

NameDescription
pipelineThe order of tool calls for one UGC video, with polling and id rules.
pricingDocumented credit cost of each action and the plan that covers it. get_credits has the live table.

TDQS

A4.4/5.0

Scored across 12 tools

Disambiguation4/5

The three clip-producing tools (create_clip, create_motion_clip, create_scene_replace_clip) all output clips and could initially be confused, but their descriptions clearly distinguish the mechanisms (animate a look, copy a driver's motion, replace a person in a user video). Other tools (list_characters vs list_images, get_video vs download_video, get_credits, list_hooks, merge_ad) each have clearly distinct roles.

Naming Consistency5/5

Every tool follows a consistent snake_case verb_noun pattern (list_characters, create_character, create_clip, create_motion_clip, generate_image, get_video, download_video, merge_ad). No mixing of camelCase or alternate verb styles.

Tool Count5/5

12 tools is well within the ideal 3-15 range and each tool maps to a distinct step in the character→look→clip→merge→download pipeline. No redundant or filler tools.

Completeness4/5

The surface covers the full UGC generation lifecycle: character creation, look generation/listing, multiple clip creation modes, merge into finished video, status polling, download, credits, and hook suggestions. Minor gaps exist around deletion/management of characters and videos, but core workflows have no dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues