Skip to main content
Glama

Clueso

by io.clueso
OverviewDiscussionsAdmin

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
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'.
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.
after_clip_idNoInsert after this clip ID; appends at end if omitted.
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 the upload_file tool.
slide_indicesNokind='pptx' only: 0-based slide indices to insert. Omit to insert all slides.
voiceover_textNokind='video' only: post-AI voiceover script (saved as v2). Original audio is always retained as the base transcript.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. 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"
+]
  3. 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
  4. First observed

TDQS

A5/5.0
Behavior5/5

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

Beyond annotations (readOnly=false, destructive=false), the description discloses the background processing pipeline, 24-hour cache behavior, the N+1 blank-clip side effect of create_project, and the whole-project serialization requirement. There is no contradiction with annotations.

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 long description is justified by three modes and 11 parameters; it is front-loaded with the core purpose and organized into scannable bullets. Every sentence adds operational value, from mode-specific payloads to concurrency constraints.

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, absence of an output schema, and minimal annotations, the description covers mode selection, parameter combinations, alternatives, side effects, and concurrency. It is sufficiently complete for an agent to call the tool correctly without further inference.

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?

Although schema coverage is 100%, the description adds cross-parameter meaning the schema cannot express: which parameters apply to each kind, defaults like video/mp4, cache-hit semantics for auto_elements, and the no-cuts whole-upload behavior. It also warns about the N+1 blank clip count and notes that background/transition can be set at creation.

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 opens with a concrete verb and object ('Create new clips on a project') and immediately disambiguates the three source modes (blank, pptx, video). It also names the specific alternative tool (add_elements) for the video-overlay case, making it easy to distinguish from siblings.

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 gives explicit when-to-use guidance per kind, including exact parameters to pass and when to choose alternatives ('use add_elements(element_type='video') instead', 'use add_audio instead'). The concurrency directive tells the agent what not to run in parallel with this tool.

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