Skip to main content
Glama

create_clip

Export a single clip as a vertical short with burned-in captions and normalized audio. Use clip number to auto-load settings from session state.

Instructions

STEP 3 — Export a single clip as a finished vertical short (1080x1920, 9:16).

EASIEST: just pass clip_number (e.g. 3) — everything else auto-loads from session state. Output: H.264 MP4 with burned-in captions, normalized audio (-14 LUFS).

For batch export, use batch_create_clips instead. Caption styles: branded (professional), hormozi (bold/yellow), karaoke (progressive highlight), subtle (minimal). Crop modes: speaker (speaker-aware), face (face tracking), center (fixed center crop). Set keep_caption_overlay=true to retain a ProRes alpha overlay for DaVinci Resolve (export_to_davinci_resolve).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoClip titleclip
logo_pathNoPath or registered asset name for PNG logo. Shown in top-left (branded style).
end_secondNoClip end time in seconds. Auto-loaded from clip_number if omitted.
outro_pathNoPath to an outro video to append at the end of the clip
video_pathNoPath to the original podcast video. Auto-loaded from session state if clip_number is provided.
clip_numberNoExport a suggested clip by its number (from suggest_clips). Auto-fills video_path, start/end times, title, and transcript_words from session state.
start_secondNoClip start time in seconds. Auto-loaded from clip_number if omitted.
caption_styleNoCaption stylehormozi
crop_strategyNoCropping strategyspeaker
transcript_wordsNoWord-level timestamps. Auto-loaded from session state if omitted.
allow_ass_fallbackNoAllow ASS caption fallback if Remotion rendering fails (default: false)
keep_caption_overlayNoKeep ProRes 4444 alpha caption overlay beside the render (for DaVinci Resolve export). Returns caption_overlay_path and cropped_source_path.
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses output format (H.264 MP4 with burned-in captions, normalized audio), auto-loading behavior from session state, and optional features like keep_caption_overlay. It does not cover error conditions or permissions, but is generally thorough.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise yet comprehensive. It is well-structured with a clear title-like line, easy usage tip, output info, sibling alternative, and a list of options. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations or output schema, the description covers key aspects: purpose, easy usage, output format, key parameters, and sibling differentiation. It could mention error handling or return value structure, but overall it is fairly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, baseline is 3. The description adds significant value by explaining the easy usage via clip_number, caption styles, crop modes, and the purpose of keep_caption_overlay beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Export a single clip as a finished vertical short (1080x1920, 9:16).' It uses a specific verb (export) and resource (clip), and distinguishes from the sibling tool batch_create_clips by directing users to it for batch operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit usage guidance with 'EASIEST: just pass clip_number' and mentions an alternative for batch export. It does not explicitly state when not to use, but the alternative implies the condition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nmbrthirteen/podcli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server