Skip to main content
Glama

clipkit

by dev.clipkit

Compose a designed promo from prebuilt scenes (one fast option)

create_promo
Destructive

Assemble a designed-looking promo/intro/product/data video from the Clipkit pattern library: give an ordered list of SCENES and the words, and it bakes in the camera, glass, lighting, motion blur, timing, and layout, then returns an editor link. This is a FAST option when a conventional promo structure fits — it is NOT the only way to make a video and NOT a default; for anything specific or original, author the JSON yourself and call set_project (the full creative range). When you do use this, MIX scene types to fit the brief and vary the structure — a video can be a single kinetic headline, three title cards, a showcase montage, or a data explainer; you do NOT need a hero or a cta. Scene types: hero (glass-orb logo reveal: wordmark, tagline?), kinetic (letter-fly headline: text, subtitle?), showcase (a screenshot tilted in 3D: screenshot URL), title (full-frame title card: headline, kicker?, subtitle?), cta (closing card with a glass button: wordmark, tagline?, cta), stats (hero numbers: stats[{label,current,previous?}], title?), bars (bar chart: bars[{label,value,previous?}], title?), ranking (top-N list: items[{label,value}], title?), pie (pie cards: cards[{label,value,total,previous?}], title?). The data scenes (stats/bars/ranking/pie) look best with theme "mux".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
themeNoVisual theme. Default "cinematic" (dark, serif, premium).
widthNoDefault 1920.
heightNoDefault 1080.
scenesYesOrdered scenes; mix types to fit the brief — you do NOT need hero/cta. e.g. a single [{type:"kinetic",text:"…"}], a sequence [{type:"title",headline:"…"},{type:"showcase",screenshot:"…"},{type:"title",headline:"…"}], or a data piece [{type:"ranking",title:"…",items:[…]}]
project_idNoWhich project to act on — the id returned by create_project / set_project / create_promo / load_project. ALWAYS pass it once a project exists in this conversation; omitting it on a build tool creates a brand-new project. (Omit only on the local stdio server working a single project.)
motion_blurNoSupersampled motion-blur samples (≥2 enables it — nicer but slower to render). Default off.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthNo
heightNo
durationNo
editor_urlNo
project_idYes
scene_countYes

TDQS

A4.7/5.0
Behavior4/5

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

The description discloses key behaviors: it bakes in camera, glass, lighting, motion blur, timing, and layout, and returns an editor link. While annotations cover destructive/read-only hints, the description adds context about the output and scene variety. It doesn't mention project creation/overwrite explicitly, but that is covered by schema and the overall framing.

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 long but every sentence earns its place: it gives a one-sentence overview, usage guidance, scene-type cheat sheet, and a theming tip. It is front-loaded with the main purpose and avoids redundancy.

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

Completeness5/5

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

Given the tool's complexity (nine scene types) and rich schema, the description is remarkably complete. It covers what the tool does, when to use it, alternatives, scene types with their parameters, and a best-practice theming tip. It also mentions the output (editor link).

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description adds value by explaining each scene type's purpose and required fields (e.g., 'hero (glass-orb logo reveal: wordmark, tagline?)') and recommending 'theme mux' for data scenes. This enriches the schema's raw field definitions.

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 what the tool does: 'Assemble a designed-looking promo/intro/product/data video from the Clipkit pattern library' with a specific verb and resource. It also distinguishes itself from siblings by positioning this as 'one fast option' and explicitly contrasting with set_project for full creative control.

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

Usage Guidelines5/5

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

It explicitly says when to use it ('FAST option when a conventional promo structure fits') and when not to ('NOT a default; for anything specific or original, author the JSON yourself and call set_project'). It also gives practical guidance to 'MIX scene types to fit the brief and vary the structure'.

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

All clipkit toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: project lifecycle (create, set, load, get, describe, validate), element manipulation (add, edit, delete), asset ingestion, preview, promo creation, schema access, and documentation. No two tools overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern, e.g., create_project, add_element, describe_project. No deviations or mixed conventions.

Tool Count5/5

15 tools is well-scoped for a video editing server, covering project management, element editing, asset handling, preview, validation, and promo generation without being excessive or sparse.

Completeness4/5

Core CRUD operations for projects and elements are covered, along with asset ingestion, schema access, and preview. However, the critical render_video tool is mentioned in descriptions but missing from the tool list, creating a notable gap in the workflow.

Resources