Clueso

Add clips to project

add_clips

Create new clips on a project. One tool, three 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.)

All variants accept after_clip_id to control insertion position; appends at end if omitted.

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

TableJSON Schema

Name	Required	Description
`cuts`	No	kind='video' only: per-clip cuts. Each entry becomes one inserted clip. Omit to insert the full upload as a single clip.
`kind`	Yes	Source for the new clips: 'blank' \| 'pptx' \| 'video'.
`clips`	No	kind='blank' only: one entry per blank clip. Optionally set background_color/background + transition per clip at creation — no follow-up update_clips needed.
`title`	No	kind='video' only: clip title (default 'Video').
`mime_type`	No	kind='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_id`	Yes	Project (guide) ID.
`after_clip_id`	No	Insert after this clip ID; appends at end if omitted.
`auto_elements`	No	kind='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_id`	No	kind='pptx' or 'video': mcp_upload_id from the upload_file tool.
`slide_indices`	No	kind='pptx' only: 0-based slide indices to insert. Omit to insert all slides.
`voiceover_text`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 15, 2026

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"
+]

Changed1 schema field changedOct 12, 2026

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."

Changed4 schema fields changedSep 22, 2026

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"
+]

Changed4 schema fields changedSep 22, 2026

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"
+]

Changed7 schema fields changedSep 17, 2026
- 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
```
First observedAug 11, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only establish the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false). The description adds substantial beyond-schema behavior: a concurrency/conflict-domain rule (serialize against any mutation on the same project_id), the async download→transcribe→insert pipeline, and a 24h cache that flips cache hits to synchronous and clones the originating run's auto-elements.

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?

Front-loads purpose, then organizes the three modes as scannable bullets with parameter lists, and closes with the concurrency constraint. Given 11 parameters and three operating modes, nearly every sentence carries non-redundant operational detail; nothing is filler.

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?

No output schema exists, so the description must carry the return/behavior burden, and it does: async vs. synchronous returns, cache semantics, insertion position, and the overlay/add_audio alternatives are all covered. For an 11-param, three-mode mutation tool this is complete enough to call correctly.

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 coverage is 100%, so the schema already documents each field and the baseline is 3. The description goes further by mapping parameters to modes (clips→blank, cuts/mime_type/title/voiceover_text/auto_elements→video, mcp_upload_id/slide_indices→pptx) and clarifying interactions such as N blanks yielding N+1 clips due to the pre-existing clip 0, which the schema alone does not convey.

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?

States a specific verb+resource ('Create new clips on a project') and immediately decomposes into three named modes (blank, pptx, video) with the parameters that select each. It explicitly distinguishes itself from siblings add_elements (overlay vs. insert) and add_audio (music vs. sequential clip), so an agent can route correctly without opening a 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?

Gives explicit when-to-use guidance per kind, including the overlay exception ('to overlay a video ONTO an existing clip ... use add_elements instead'), the background-music exception pointing to add_audio, and the create_project clip-0 caveat. Alternatives and exclusions are stated directly rather than inferred.

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

All Clueso tools Inspect

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.

Add clips to project

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources