Skip to main content
Glama

Clueso

by io.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
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.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations (readOnlyHint=false, destructiveHint=false) are basic, but the description adds extensive behavioral details: concurrency constraints, 24h caching, background pipeline for video, and the note that create_project already creates clip 0. No contradictions.

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?

The description is well-structured with clear sections for each kind, but it is somewhat long due to thorough details (e.g., caching, concurrency). Every sentence contributes value, though minor trimming could improve conciseness.

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 all aspects: parameter usage, side effects, ordering, concurrency, alternatives, and caching behavior. However, it lacks explicit mention of the return value (what the tool outputs after creating clips), which would be useful given no output schema. Still very complete overall.

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%, yet the description adds significant context: for blank clips, it explains that background/transition can be set at creation; for video kind, clarifies mime_type default and the effect of omitting cuts; for pptx, slide_indices optional. All parameter meanings are enriched beyond raw schema.

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 it creates new clips on a project and distinguishes three sources (blank, pptx, video) with explicit use cases. It differentiates from sibling tools like add_elements for video overlays and add_audio for background music.

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?

Explicitly tells when to use each kind and when not (e.g., for overlays use add_elements, for background music use add_audio). Provides concurrency advice: serialize mutations on the same project, do not run in parallel with other mutations.

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
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.1/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but there is notable overlap between remove_elements and remove_from_project(target='element'), which both remove elements from a clip. This duplication could cause an agent to misselect. Otherwise, tools like add_clips, add_elements, add_audio, and analyze_audio are well-differentiated.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (e.g., add_clips, create_project, get_clip, update_elements). There are no camelCase or mixed conventions. Even compound names like voiceover_batch and auto_sync fit the pattern. This makes the tool set predictable for an agent.

Tool Count2/5

With 40 tools, the set is significantly larger than the 3-15 range that typically earns its place. While the domain of video creation is broad, several tools seem redundant (remove_elements vs remove_from_project) or narrowly scoped (get_design_guide, get_element_schema), inflating the count. The number feels heavy for the apparent scope.

Completeness4/5

The tool surface covers most lifecycle operations: create, read, update, delete for projects, clips, elements, audio, articles, and clueprints. Minor gaps exist, such as no explicit tool to delete a voiceover (only mute via update_clips) and no folder management beyond listing. Overall, agents can accomplish full workflows with few workarounds.

Resources