Skip to main content
Glama

Multi-scene composition

start_composition

Estimate, start or retry a multi-scene video composition. Estimate first: action "estimate" returns the credit cost and spends nothing. "start" begins the composition, which needs a prompt. "retry" re-runs a composition by compositionId. Spends Galatic.AI credits. Returns a job id; poll get_job_status with kind "composition".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "start_composition"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoVideo model id for the scenes, from list_models.
actionYesestimate: cost only, spends nothing. start: begin a composition. retry: re-run compositionId.
promptNoWhat the composition is about. Required for start.
contextYesExplain 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."
mixModeNoHow narration and music are mixed.
captionsNoCaption settings, passed through to the composition.
costTierNoCost tier for the scenes. It sets the price and the maximum duration.
llm_modelYesThe 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.
musicConfigNoBackground music settings for the composition.
videoConfigNoScene video settings such as duration, costTier and extendMode ("multi-scene" or "extend").
voiceConfigNoNarration voice. provider is one of polly, polly-generative, elevenlabs-clone or skip.
compositionIdNoRequired for retry: the id of the composition to re-run.
galleryAssetsNoLibrary items to use as scene material, passed through as the route expects.
narrationTextNoNarration script, read in the voice set by voiceConfig.
compositionTypeNoWhat kind of piece this is. It decides how the result is filed in the library.
conversation_idNoPass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.
targetDurationSecNoTarget length of the whole composition, in seconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"estimate: cost only, spends nothing. start: begin a composition. retry: re-run compositionId."
    • addedInput schema / properties / captions / description
      Added value: +"Caption settings, passed through to the composition."
    • addedInput schema / properties / compositionId / description
      Added value: +"Required for retry: the id of the composition to re-run."
    • addedInput schema / properties / compositionType
      Added value: +{
      +  "description": "What kind of piece this is. It decides how the result is filed in the library.",
      +  "enum": [
      +    "music-video",
      +    "commercial",
      +    "short",
      +    "cartoon",
      +    "custom"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / costTier / description
      Added value: +"Cost tier for the scenes. It sets the price and the maximum duration."
    • addedInput schema / properties / costTier / enum
      Added value: +[
      +  "budget",
      +  "standard",
      +  "premium",
      +  "hybrid"
      +]
    • addedInput schema / properties / galleryAssets / description
      Added value: +"Library items to use as scene material, passed through as the route expects."
    • addedInput schema / properties / mixMode / description
      Added value: +"How narration and music are mixed."
    • addedInput schema / properties / mixMode / enum
      Added value: +[
      +  "narration-over-music",
      +  "music-only",
      +  "narration-only",
      +  "full-mix"
      +]
    • addedInput schema / properties / model / description
      Added value: +"Video model id for the scenes, from list_models."
    • addedInput schema / properties / musicConfig / description
      Added value: +"Background music settings for the composition."
    • addedInput schema / properties / narrationText / description
      Added value: +"Narration script, read in the voice set by voiceConfig."
    • addedInput schema / properties / prompt / description
      Added value: +"What the composition is about. Required for start."
    • addedInput schema / properties / targetDurationSec / description
      Added value: +"Target length of the whole composition, in seconds."
    • addedInput schema / properties / videoConfig / description
      Added value: +"Scene video settings such as duration, costTier and extendMode (\"multi-scene\" or \"extend\")."
    • addedInput schema / properties / voiceConfig / description
      Added value: +"Narration voice. provider is one of polly, polly-generative, elevenlabs-clone or skip."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only say non-readOnly, non-idempotent, non-destructive; the description adds the material facts: credits are spent, estimate spends nothing, and the call is asynchronous returning a job id. That is genuine value beyond the structured hints. It stops short of saying what happens on partial failure or whether a started job can be cancelled.

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?

Five short sentences, front-loaded with the capability then ordered by workflow: estimate, start, retry, cost, polling. No filler and no repetition of schema content beyond what is needed to explain sequencing.

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?

For a 17-parameter, nested-object, no-output-schema tool, the description covers the essential call pattern: action selection, prerequisites, cost implication, and how to retrieve the result. The heavy configuration surface (videoConfig, voiceConfig, captions, galleryAssets) is left entirely to the schema, which is defensible at 100% coverage but means the description gives no orientation to the tool's main knobs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all 17 parameters are already documented in the schema, which sets the baseline at 3. The description only restates the action-to-parameter coupling (prompt for start, compositionId for retry) that the schema already states verbatim. It adds nothing about costTier, compositionType, or the nested config objects.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific multi-verb capability (estimate/start/retry) applied to a specific resource (multi-scene video composition), with each action's meaning spelled out in one clause. It doesn't explicitly contrast itself with near-neighbors like generate_video or generate_music_video, so the agent must infer the boundary from the word 'multi-scene' alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Estimate first" is explicit ordering guidance, and the description ties each action to its prerequisite (start needs a prompt, retry needs compositionId). It also routes the agent forward to get_job_status with kind "composition". Missing is when to prefer this over the sibling single-clip generators.

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.