clipugc
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLIPUGC_API_KEY | No | Your 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_URL | No | Optional. 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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_charactersA | List ClipUGC AI characters (AI influencers). Same as |
| create_characterA | Create a new AI character from a plain-text description. Same as |
| generate_imageA | Generate one or more new looks (reference images) of an existing character. Same as |
| 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 |
| create_clipA | Animate a character look (or your own photo) into a short video clip. Same as |
| create_motion_clipA | Animate a character look (or your own photo) by copying the motion of a driver video. Same as |
| 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 |
| 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 |
| get_videoA | Get the current status of a clip (kind "clip", default; same as |
| download_videoA | Download a completed clip (kind "clip", default; same as |
| get_creditsA | Return the authenticated user's credit balance and the live per-action credit costs (keys |
| list_hooksA | Get AI-suggested hook texts (the short attention-grabbing line burned over a UGC video). Same as |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| make_ugc_video | Walks 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_influencer | Creates a private ClipUGC AI influencer from a plain description and waits for its first photo. |
| hook_ideas | Asks 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
| Name | Description |
|---|---|
| pipeline | The order of tool calls for one UGC video, with polling and id rules. |
| pricing | Documented credit cost of each action and the plan that covers it. get_credits has the live table. |
TDQS
Scored across 12 tools
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.
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.
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.
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.