Skip to main content
Glama
Sign In

Clueso

by io.clueso
OverviewDiscussionsAdmin

Add clips to project

add_clips

Create new clips on a project. One tool, four sources:

  • kind="blank": empty slide clips you'll populate with add_elements / generate_media. Pass clips: [{title?, duration?}, ...]. Note: create_project already creates clip 0; calling with N blank entries gives N+1 clips total.

  • kind="pptx": extract slides from an uploaded .ppt/.pptx. Pass mcp_upload_id (from upload_file), optional slide_indices. Each slide becomes a slide_clip with native text/image/shape elements pre-populated.

  • kind="video": cut clips from an uploaded video/audio. Pass mcp_upload_id and optionally mime_type (default video/mp4), title, voiceover_text, cuts: [{start_seconds, end_seconds, heading?}], auto_elements. Without cuts the whole upload becomes one clip. Pipeline (download → transcribe → insert) runs in the background; subsequent calls on the same upload hit a 24h cache and return synchronously. (To overlay a video ONTO an existing clip — picture-in-picture, b-roll, background loop — rather than insert it as its own clip, use add_elements(element_type='video') instead.)

    • Re-cut clips already on the timeline: pass source_start_clip_id, source_end_clip_id (a run of video clips from one recording, inclusive) and cuts instead of an upload. The run is replaced in place by one clip per cut; cut seconds are on the run's own clock (0 = start of the first clip). Recording cut out between the clips counts back in, so a cut across it restores that footage (restored_gap_seconds).

  • kind="template": one clip from a clip template (find(type='clip_templates')). Pass template_id and text_overrides (strings for the template's text elements in document order; a missing or empty one keeps the placeholder — fill them with the user's words). after_clip_id is REQUIRED: ask the user where it goes, never guess. Insert only; a template whose aspect ratio differs from the project is refused (aspect_mismatch — pick another). The clip inherits the project's voice.

All variants accept after_clip_id to control insertion position; appends at end if omitted (except kind="template").

Concurrency: whole-project mutation (conflict domain: the entire project) — serialize. Do not run it in parallel with ANY other mutation on the same project_id, including element/voiceover edits; run them one at a time. (Mutations to different projects run in parallel freely.)

Input Schema

NameRequiredDescriptionDefault
cutsNokind='video' only: per-clip cuts. Each entry becomes one inserted clip. Omit to insert the full upload as a single clip.
kindYesSource for the new clips: 'blank' | 'pptx' | 'video' | 'template'.
clipsNokind='blank' only: one entry per blank clip. Optionally set background_color/background + transition per clip at creation — no follow-up update_clips needed.
titleNokind='video' only: clip title (default 'Video').
mime_typeNokind='video' only: MIME type (default 'video/mp4'). Audio MIME types insert the file as a sequential clip with auto-TTS; for background music, use add_audio instead.
project_idYesProject (guide) ID.
template_idNokind='template' only: template_id from find(type='clip_templates').
after_clip_idNoInsert after this clip ID; appends at end if omitted. kind='video': '' inserts at the front.
auto_elementsNokind='video' only: when true, run auto-element detection (zooms, spotlights, blurs). Default false. Only meaningful on cache miss; cache hits clone the originating run's auto-elements.
mcp_upload_idNokind='pptx' or 'video': mcp_upload_id from upload_file, or a Clueso upload_id (or its S3 key).
slide_indicesNokind='pptx' only: 0-based slide indices to insert. Omit to insert all slides.
text_overridesNokind='template' only: text for the template's text elements, in document order.
voiceover_textNokind='video' only: post-AI voiceover script (saved as v2). Original audio is always retained as the base transcript. Bracketed emotion tags ([excited], [whispers]) are performed, not spoken; <pause:1.5s> is exact timed silence.
source_end_clip_idNokind='video' re-cut: last clip of the run (inclusive).
source_start_clip_idNokind='video' re-cut: first clip of the run to re-cut (inclusive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / after_clip_id / description
      Previous value: -"Insert after this clip ID; appends at end if omitted."New value: +"Insert after this clip ID; appends at end if omitted. kind='video': '' inserts at the front."
    • changedInput schema / properties / clips / items / properties / background / description
      Previous value: -"Full background object from find(type='backgrounds'), set at creation."New value: +"Background set at creation: an object from find(type='backgrounds'), or { src, media_type?, padding?, border_radius?, shadow?, volume? } as in update_clips."
    • changedInput schema / properties / kind / description
      Previous value: -"Source for the new clips: 'blank' | 'pptx' | 'video'."New value: +"Source for the new clips: 'blank' | 'pptx' | 'video' | 'template'."
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "blank",
-  "pptx",
-  "video"
-]New value: +[
+  "blank",
+  "pptx",
+  "video",
+  "template"
+]
    • changedInput schema / properties / mcp_upload_id / description
      Previous value: -"kind='pptx' or 'video': mcp_upload_id from the upload_file tool."New value: +"kind='pptx' or 'video': mcp_upload_id from upload_file, or a Clueso upload_id (or its S3 key)."
    • addedInput schema / properties / source_end_clip_id
      Added value: +{
+  "description": "kind='video' re-cut: last clip of the run (inclusive).",
+  "type": "string"
+}
    • addedInput schema / properties / source_start_clip_id
      Added value: +{
+  "description": "kind='video' re-cut: first clip of the run to re-cut (inclusive).",
+  "type": "string"
+}
    • addedInput schema / properties / template_id
      Added value: +{
+  "description": "kind='template' only: template_id from find(type='clip_templates').",
+  "type": "string"
+}
    • addedInput schema / properties / text_overrides
      Added value: +{
+  "description": "kind='template' only: text for the template's text elements, in document order.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Changed4 schema fields changed
    • addedInput schema / properties / clips / items / properties / transition / properties / bezier
      Added value: +{
+  "description": "Custom easing of the transition, CSS cubic-bezier [x1, y1, x2, y2], e.g. [0.34, 1.56, 0.64, 1] for a slight bounce. Honoured by flip; omit for its default ease-in-out.",
+  "items": {
+    "type": "number"
+  },
+  "maxItems": 4,
+  "minItems": 4,
+  "type": "array"
+}
    • changedInput schema / properties / clips / items / properties / transition / properties / color / description
      Previous value: -"Hex color, honoured by fadeToColor (default #000000), colorWipe (default #073cad) and rainbowWipe (default #D43F8C)."New value: +"Hex color, honoured by fadeToColor (default #000000), colorWipe (default #073cad), rainbowWipe (default #D43F8C) and flip (the backdrop behind the turning card, default #000000)."
    • changedInput schema / properties / clips / items / properties / transition / properties / direction / description
      Previous value: -"Direction, honoured only by some types: rainbowWipe and cornerWipe take topLeft/topRight/bottomLeft/bottomRight (default topRight); colorWipe takes left or right (default right); stack and pushPull take left/right/top/bottom (default right). Ignored by dissolve, circleWipe and fadeToColor."New value: +"Direction, honoured only by some types: rainbowWipe and cornerWipe take topLeft/topRight/bottomLeft/bottomRight (default topRight); colorWipe takes left or right (default right); stack and pushPull take left/right/top/bottom (default right); flip takes horizontalLeft/horizontalCenter/horizontalRight/verticalTop/verticalCenter/verticalBottom (default horizontalCenter) — the axis it turns about (horizontal = left↔right, vertical = up↔down) and the line it turns on (an edge, or the middle for a card flip). Ignored by dissolve, circleWipe and fadeToColor."
    • changedInput schema / properties / clips / items / properties / transition / properties / type / enum
      Previous value: -[
-  "circleWipe",
-  "rainbowWipe",
-  "cornerWipe",
-  "stack",
-  "colorWipe",
-  "dissolve",
-  "pushPull",
-  "fadeToColor"
-]New value: +[
+  "circleWipe",
+  "rainbowWipe",
+  "cornerWipe",
+  "stack",
+  "colorWipe",
+  "dissolve",
+  "pushPull",
+  "fadeToColor",
+  "flip"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / voiceover_text / description
      Previous value: -"kind='video' only: post-AI voiceover script (saved as v2). Original audio is always retained as the base transcript."New value: +"kind='video' only: post-AI voiceover script (saved as v2). Original audio is always retained as the base transcript. Bracketed emotion tags ([excited], [whispers]) are performed, not spoken; <pause:1.5s> is exact timed silence."
  4. Changed4 schema fields changed
    • removedInput schema / properties / context
      Removed value: -{
-  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
-  "type": "string"
-}
    • removedInput schema / properties / conversation_id
      Removed value: -{
-  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
-  "type": "string"
-}
    • removedInput schema / properties / llm_model
      Removed value: -{
-  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "kind",
-  "project_id",
-  "context",
-  "llm_model"
-]New value: +[
+  "kind",
+  "project_id"
+]
  5. Changed4 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
    • addedInput schema / properties / conversation_id
      Added value: +{
+  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
+  "type": "string"
+}
    • addedInput schema / properties / llm_model
      Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "kind",
-  "project_id"
-]New value: +[
+  "kind",
+  "project_id",
+  "context",
+  "llm_model"
+]
  6. Changed7 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / clips / items / additionalProperties
      Removed value: -false
    • addedInput schema / properties / clips / items / properties / background / propertyNames
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / clips / items / properties / transition / additionalProperties
      Removed value: -false
    • removedInput schema / properties / cuts / items / additionalProperties
      Removed value: -false
    • addedInput schema / properties / slide_indices / items / maximum
      Added value: +9007199254740991
  7. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes far beyond the annotations, which only say non-readOnly/non-destructive/closed-world. It discloses the async background pipeline (download → transcribe → insert), the 24h cache that makes later calls synchronous, the aspect_mismatch refusal, gap restoration semantics (`restored_gap_seconds`), and a whole-project concurrency/serialization rule that annotations cannot express.

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

Conciseness4/5

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

Front-loaded with a one-line summary and then a clean per-`kind` bullet structure that mirrors the enum, so scanning is fast. It is long and carries a few dense parenthetical asides (re-cut clock semantics, auto_elements cache behavior), but with 15 parameters and four modes little is wasted.

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?

Covers mode selection, prerequisites (upload_file), positioning, side effects, failure modes, and concurrency — nearly everything needed to call it correctly. The one gap is that with no output schema, it never says what comes back (e.g. created clip IDs or job handles), which an agent chaining follow-up edits would want.

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?

Schema coverage is 100% so the baseline is 3, but the description adds genuine meaning on top: cut seconds are on the run's own clock (0 = start of first clip), `text_overrides` map to text elements in document order with empty values keeping placeholders, `after_clip_id` is REQUIRED for templates but optional elsewhere, and '' inserts at the front for video.

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?

Opens with a specific verb+resource ('Create new clips on a project') and immediately decomposes the tool into its four source modes via the required `kind` parameter. Each mode is described concretely enough that an agent can tell which one it wants without opening the schema.

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?

Explicit routing away from siblings: overlay video onto an existing clip → add_elements(element_type='video'), background music → add_audio, clip templates → find(type='clip_templates'). Also gives when-not-to assumptions (create_project already makes clip 0) and an explicit instruction to ask the user rather than guess `after_clip_id` for templates.

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

All Clueso toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources