Skip to main content
Glama

Clueso

by io.clueso

Add audio track

add_audio

Add a music track or sound effect that plays as a project-level audio layer over all clips. Does NOT consume a clip slot. Use this for background music or a soundtrack that should play under the existing timeline. (For inserting an audio file as its own sequential clip with auto-transcription, use add_clips(kind='video') with an audio mime_type instead.)

  • type="music": requires src, name, source_duration. src is either the src from a find(type='music') result, or an mcp_upload_id (prefixed mup_) from upload_file — upload ids resolve to a presigned URL server-side. For a Freesound result the src is an opaque handle; pass it through unchanged and Clueso downloads + hosts the original server-side (do not try to fetch it yourself). Get source_duration from the find result, or from analyze_audio mode='features' (data.duration_ms / 1000). Optional: guide_start_time, guide_end_time, music_start_time, music_end_time (trim the source track), volume, loop, fade_in, fade_out.

  • type="sfx": pass the src, name, and source_duration from a find(type='sfx') result, plus guide_start_time (Freesound src is an opaque handle, resolved server-side just like music). Optional: volume. (Legacy: a fixed-library sfx_key like 'whoosh' still works instead of src.)

Concurrency: whole-project mutation (conflict domain: the entire project) — serialize; do not run in parallel with ANY other mutation on the same project_id (including element/voiceover edits). Size your clips BEFORE calling add_audio, or pass guide_end_time explicitly — the default ('end of project') is captured at call time and will NOT auto-extend if clips are added or resized afterwards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
srcNoAudio source. For type='music' (required) or a stock type='sfx': the `src` from a find(type='music'|'sfx') result (may be an opaque Freesound handle — pass as-is), or an mcp_upload_id (prefixed 'mup_') from upload_file. Not needed for legacy fixed-library sfx (use sfx_key).
loopNoLoop the track if project is longer than the source. Music only. (default: false)
nameNoTrack/effect name. From the find result, or any descriptive label when using mcp_upload_id. Required for type='music' and for stock type='sfx' (passed via src).
typeYesAudio type: 'music' or 'sfx'
volumeNoVolume as percent (0–100). Default: 50 for music, 80 for sfx.
fade_inNoFade-in duration in seconds. Music only. (default: 0.5)
sfx_keyNoLEGACY fixed-library SFX key (e.g. 'whoosh', 'pop', 'click'). Optional alternative to src for type='sfx'. Prefer the src/name/source_duration from a find(type='sfx') result.
fade_outNoFade-out duration in seconds. Music only. (default: 0.5)
project_idYesThe project ID
guide_end_timeNoWhen to stop playing (seconds). Music only. Default = end of project AT CALL TIME — captured once at insert and NOT recomputed when clips are later added or resized. Pass an explicit value (e.g. the intended final project duration) when adding audio before clips are sized.
music_end_timeNoOut-point within the SOURCE track (seconds) — trims where playback ends in the music file. Music only. Default = source_duration.
source_durationNoSource duration in seconds. From the find result, or analyze_audio mode='features' (data.duration_ms / 1000). Required for type='music' and for stock type='sfx' (passed via src).
guide_start_timeNoWhen to start playing in the guide timeline (seconds). Required for type='sfx', optional for music (default 0).
music_start_timeNoIn-point within the SOURCE track (seconds) — trims where playback begins in the music file. Music only. Default 0 (start of source).

TDQS

A4.9/5.0
Behavior5/5

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

Annotations provide readOnlyHint=false, destructiveHint=false, openWorldHint=false. The description goes far beyond by explaining the non-clip-slot nature, differentiating music vs sfx behaviors, and detailing critical runtime semantics like guide_end_time being captured at call time and not auto-extending. 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.

Conciseness4/5

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

The description is well-structured with type-specific bullet points, a concurrency note, and a clear front-loaded purpose. While fairly long, every sentence adds value and aligns with the tool's complexity (14 params, two types). Could be slightly tighter, but the organization is logical and easy to scan.

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 14 parameters, 2 required, no output schema, and complex behavior (type-specific logic, concurrency domain, default timing caveats), the description covers the necessary details for correct invocation. It addresses edge cases (legacy sfx_key, mcp_upload_id, guide_end_time capture behavior) and provides actionable guidance for an AI agent.

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% already, but the description adds significant extra meaning: for src, it explains the opaque Freesound handle and mcp_upload_id usage; for source_duration, it cites analyze_audio as an alternative; for guide_end_time, it elaborates on the capture-time default. This greatly enhances the agent's understanding beyond the schema alone.

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 uses a specific verb ('Add') and clearly identifies the resource as a 'project-level audio layer over all clips'. It explicitly states it does NOT consume a clip slot, distinguishing it from the sibling tool add_clips. The contrast with add_clips(kind='video') for audio-as-clip further sharpens purpose clarity.

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?

The description explicitly states when to use the tool ('background music or a soundtrack that should play under the existing timeline') and when NOT to use it (for inserting an audio file as its own sequential clip, referencing add_clips). It also provides concurrency guidance ('serialize; do not run in parallel with ANY other mutation') and warns about guide_end_time behavior. This is comprehensive and actionable.

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