Skip to main content
Glama

Doseedo Film Score: spot a video, play your score on AI instruments, mix it to picture

Stems → a DAW session

doseedo_session_from_stems

Build a native DAW PROJECT from stems: each stem on its own audio track from bar 1, optional MIDI tracks (the written parts) beside them, on your tempo (bpm or tempo_map) — Logic Pro (.logicx) or Ableton Live (.als), zipped. The deliverable after doseedo_render_score (pass from_job: its job_id and the stems, MIDI and tempo come from that job) or after any renders / separations you made (stems: [{name, audio_url}] — result links work as-is). After doseedo_mix add mix_job: each track at that mix's level and pan, the mix as a muted reference track. Async: job_id → doseedo_wait_task (~30–90 s) → file (pre-signed zip, curl -o session.zip , 24 h). Cancel: the plane has no stop for a running session build — it runs to completion (credits spent), the job ends as canceled and its output is discarded. Only a job still queued at the plane is refunded by the plane's own failure refund.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "doseedo_session_from_stems"
  }
}

Input Schema

NameRequiredDescriptionDefault
bpmNoProject tempo (default 120).
cuesNoMCP: ONE session for a whole scored film — [{cue: "1M1", start_s, from_job: <its doseedo_render_score job>, mix_job?: <its doseedo_mix job>, emotion?}] (≤ 12 cues, from the cue sheet's start_s). Every cue's stems and MIDI land on one timeline at its start, on ONE tempo map (each cue's own tempo_map joined, each cue's bar 1 on a bar line), a marker per cue, each track at its cue's mix level and pan, each cue's mix as a muted reference. Replaces from_job / mix_job / stems.
nameNoProject name — the project inside the zip, and the zip itself downloads as <name>_session.zip.
stemsNo[{name, audio_url | audio_key, gain_db?, pan?, mute?, position_beats?}] — the audio tracks, in order.
videoNoThe film the music is written to: {video_key: the ingest/ key of your upload (doseedo_get_upload_url), name?, start_s?}. It is re-encoded lean (720p) and travels inside the project: REAPER gets a muted video track, Logic Pro gets its Movie (inside the package; Logic finds it by name). Ableton projects are built without it (the answer says so).
targetNoWhich DAW (default logic): Logic Pro (.logicx), Ableton Live (.als) or REAPER (.rpp + media, with the film as a video track). Or a VIDEO EDITOR, for whoever cuts the picture: premiere (Premiere Pro: an FCP7 XML), finalcut (Final Cut Pro: an FCPXML) or resolve (DaVinci Resolve: both). An editor project is the film on V1, every stem as its own clip at its position (one track per part across the cues), a marker per cue, the sequence at the film's own start timecode, with its media beside it (48 kHz, 24-bit). Each stem's gain_db and pan are printed into its file, so clips sit at unity; midi_tracks and the tempo map are not written (a timeline holds none).
markersNoArrangement markers [{name, beat}] — beat 0 = bar 1 on the project's tempo map. A scored film's cues are written as markers by `cues`.
mix_jobNoMCP: a doseedo_mix job_id — every track takes that mix's level and pan, and the mix itself rides along as a muted reference track "Mix (doseedo)".
from_jobNoMCP: a doseedo_render_score job_id — its stems, parts' MIDI and tempo are used (no other input needed).
mixgraphNoA mix document (doseedo_mix → mixgraph): each stem named in it takes its strip's gain_db and pan. The EQ, compression, reverb and rides are not written into the project.
tempo_mapNoTempo changes [{beat, bpm}] for the project.
midi_tracksNoOptional MIDI tracks: [{name, notes:[{pitch, start_beats, duration_beats, velocity?}]}].
session_beatsNoLength of the session in beats (the tempo map is written this far; default: the last note). `cues` sets it.
time_signatureNoMeter (default 4/4).
idempotency_keyNoOptional. Any unique string for THIS request (e.g. a UUID). Re-sending the same call with the same key after a timeout returns the same job instead of starting a second one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / target / description
      Previous value: -"Which DAW (default logic): Logic Pro (.logicx), Ableton Live (.als) or REAPER (.rpp + media, with the film as a video track)."New value: +"Which DAW (default logic): Logic Pro (.logicx), Ableton Live (.als) or REAPER (.rpp + media, with the film as a video track). Or a VIDEO EDITOR, for whoever cuts the picture: premiere (Premiere Pro: an FCP7 XML), finalcut (Final Cut Pro: an FCPXML) or resolve (DaVinci Resolve: both). An editor project is the film on V1, every stem as its own clip at its position (one track per part across the cues), a marker per cue, the sequence at the film's own start timecode, with its media beside it (48 kHz, 24-bit). Each stem's gain_db and pan are printed into its file, so clips sit at unity; midi_tracks and the tempo map are not written (a timeline holds none)."
    • changedInput schema / properties / target / enum
      Previous value: -[
      -  "logic",
      -  "ableton",
      -  "reaper"
      -]New value: +[
      +  "logic",
      +  "ableton",
      +  "reaper",
      +  "premiere",
      +  "finalcut",
      +  "resolve"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / video / description
      Previous value: -"The film the music is written to: {video_key: the ingest/ key of your upload (doseedo_get_upload_url), name?, start_s?}. It is re-encoded lean (720p) and laid on its own muted track in the project — for REAPER today; Logic / Ableton projects are built without it (the answer says so)."New value: +"The film the music is written to: {video_key: the ingest/ key of your upload (doseedo_get_upload_url), name?, start_s?}. It is re-encoded lean (720p) and travels inside the project: REAPER gets a muted video track, Logic Pro gets its Movie (inside the package; Logic finds it by name). Ableton projects are built without it (the answer says so)."
  3. Changed6 schema fields changed
    • addedInput schema / properties / cues
      Added value: +{
      +  "description": "MCP: ONE session for a whole scored film — [{cue: \"1M1\", start_s, from_job: <its doseedo_render_score job>, mix_job?: <its doseedo_mix job>, emotion?}] (≤ 12 cues, from the cue sheet's start_s). Every cue's stems and MIDI land on one timeline at its start, on ONE tempo map (each cue's own tempo_map joined, each cue's bar 1 on a bar line), a marker per cue, each track at its cue's mix level and pan, each cue's mix as a muted reference. Replaces from_job / mix_job / stems.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "cue": {
      +        "type": "string"
      +      },
      +      "emotion": {
      +        "type": "string"
      +      },
      +      "from_job": {
      +        "type": "string"
      +      },
      +      "mix_job": {
      +        "type": "string"
      +      },
      +      "start_s": {
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "cue",
      +      "start_s",
      +      "from_job"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / markers
      Added value: +{
      +  "description": "Arrangement markers [{name, beat}] — beat 0 = bar 1 on the project's tempo map. A scored film's cues are written as markers by `cues`.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "beat": {
      +        "type": "number"
      +      },
      +      "name": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "beat"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / session_beats
      Added value: +{
      +  "description": "Length of the session in beats (the tempo map is written this far; default: the last note). `cues` sets it.",
      +  "type": "number"
      +}
    • changedInput schema / properties / target / description
      Previous value: -"Which DAW (default logic)."New value: +"Which DAW (default logic): Logic Pro (.logicx), Ableton Live (.als) or REAPER (.rpp + media, with the film as a video track)."
    • changedInput schema / properties / target / enum
      Previous value: -[
      -  "logic",
      -  "ableton"
      -]New value: +[
      +  "logic",
      +  "ableton",
      +  "reaper"
      +]
    • addedInput schema / properties / video
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "The film the music is written to: {video_key: the ingest/ key of your upload (doseedo_get_upload_url), name?, start_s?}. It is re-encoded lean (720p) and laid on its own muted track in the project — for REAPER today; Logic / Ableton projects are built without it (the answer says so).",
      +  "properties": {
      +    "name": {
      +      "type": "string"
      +    },
      +    "start_s": {
      +      "type": "number"
      +    },
      +    "video_key": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "video_key"
      +  ],
      +  "type": "object"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Project name."New value: +"Project name — the project inside the zip, and the zip itself downloads as <name>_session.zip."
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses the async contract (job_id → doseedo_wait_task, ~30–90 s), a pre-signed zip with a 24 h expiry, and the unusual cancellation semantics (a running build cannot be stopped, credits are spent, output discarded; only a still-queued job is refunded). It also discloses that video is re-encoded to 720p and omitted from Ableton projects. Minor gap: it never says what the response object looks like on the initial call, though the job_id flow is implied.

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 the deliverable, then inputs, then lifecycle — a sensible order, and near every clause carries operational information. It is dense and em-dash-heavy, with some doubling against the schema (the .logicx/.als target list appears in both description and target property).

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?

For a 15-parameter, nested-object, no-output-schema tool, the description supplies the pieces the schema cannot: the async handoff to doseedo_wait_task, the download mechanics, the refund/cancel behavior, and how the multi-cue film mode collapses the other inputs. Nothing essential for invoking it correctly appears to be missing.

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 baseline is 3; the description still earns above baseline by explaining the precedence relationship among from_job, mix_job, stems and cues (cue mode supersedes the others) and by noting from_job needs 'no other input'. It does not add much on the remaining 12 parameters beyond what the schema already states, and the target list (Logic/Ableton in prose vs. six enum values in schema) is partially duplicated.

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+scope: 'Build a native DAW PROJECT from stems', then names the three entry paths (from_job after doseedo_render_score, raw stems after renders/separations, mix_job after doseedo_mix). That differentiates it cleanly from doseedo_render_score and doseedo_mix, which are the tools that produce those upstream jobs.

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 states which upstream job types feed it and what to pass in each case ('pass from_job: its job_id'; 'stems: [{name, audio_url}] — result links work as-is'; 'after doseedo_mix add mix_job'). The schema's cues entry further says it 'Replaces from_job / mix_job / stems', giving an exclusion rule for the alternative mode.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources