Skip to main content
Glama

Create a Canvas

create_canvas
Idempotent

Make the Canvas a quote priced (spends credits) Send the same request as the quote plus its quote_id. Returns the video ids at once; poll get_video until status is completed. Upload the file in Spotify for Artists. Needs an active plan (402 plan_required without one; get_account: plan.active) and room in its storage (402 storage_full when it would not fit; get_account: storage).

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": {
      "song_id": "<song_id>",
      "quote_id": "<quote_id>"
    },
    "name": "create_canvas"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoOptional visual style
sourceNoai-video (default), ai-image, stock-photo or stock-videoai-video
qualityNoAI video model tier: standard or highstandard
secondsNoCanvas length in whole seconds, 5–8 (default 8). Spotify loops it, so no part of the song is chosen
song_idYesThe song id
metadataNoYour own JSON (an order id, for example): kept with the video and returned in its request. Quote and create with the same value
quote_idYesThe quote_id from the matching quote: the request must be identical
stock_idNoWith a stock source: the stock photo or video (search_stock with seconds) to use instead of the director's pick
directionNoOptional mood, motifs or references
performerNoA Creator workspace only: the character (list_characters with for_artist_id: one in the song's project's kit or one another project shared) who may appear, with feature_artist auto or always on an AI source. Omitted: the song's artist's character
resolutionNo1080p (1080×1920) or 720p1080p
variationsNo1–4 different Canvases
inspirationNoWhere the idea comes from: song (default; what the song means and how it sounds lead, the colors kept close to the cover, when there is one, so the two sit together in the player) or cover (the cover art's world, colors and motifs, brought to life; a song without a cover always uses song)song
callback_urlNoAn https URL to POST the finished video to (signed; see Callbacks). Quote and create with the same value
feature_artistNoWhether the Canvas shows the artist: auto (the director decides), always or never (AI sources; "always" needs the artist's character: list_characters, start_character makes one)auto

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / inspiration / default
      Previous value: -"cover"New value: +"song"
    • changedInput schema / properties / inspiration / description
      Previous value: -"Where the idea comes from: cover (default; the cover art's world, colors and motifs, brought to life) or song (its words, story and sound lead, the colors kept close to the cover so the two sit together in the player)"New value: +"Where the idea comes from: song (default; what the song means and how it sounds lead, the colors kept close to the cover, when there is one, so the two sit together in the player) or cover (the cover art's world, colors and motifs, brought to life; a song without a cover always uses song)"
  2. Changed1 schema field changed
    • changedInput schema / properties / performer / description
      Previous value: -"A Creator workspace only: the cast character (list_characters) who may appear, with feature_artist auto or always on an AI source. Omitted: the song's artist's character"New value: +"A Creator workspace only: the character (list_characters with for_artist_id: one in the song's project's kit or one another project shared) who may appear, with feature_artist auto or always on an AI source. Omitted: the song's artist's character"
  3. Changed4 schema fields changed
    • changedInput schema / properties / direction / description
      Previous value: -"Optional mood, motifs or references; the concept still comes from the cover"New value: +"Optional mood, motifs or references"
    • changedInput schema / properties / feature_artist / description
      Previous value: -"Whether the Canvas shows the artist: auto (the director decides), always or never (AI sources; needs artist photos for \"always\")"New value: +"Whether the Canvas shows the artist: auto (the director decides), always or never (AI sources; \"always\" needs the artist's character: list_characters, start_character makes one)"
    • addedInput schema / properties / inspiration
      Added value: +{
      +  "default": "cover",
      +  "description": "Where the idea comes from: cover (default; the cover art's world, colors and motifs, brought to life) or song (its words, story and sound lead, the colors kept close to the cover so the two sit together in the player)",
      +  "enum": [
      +    "cover",
      +    "song"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / performer
      Added value: +{
      +  "description": "A Creator workspace only: the cast character (list_characters) who may appear, with feature_artist auto or always on an AI source. Omitted: the song's artist's character",
      +  "pattern": "^kit_[0-9a-f-]{36}$",
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / stock_id / description
      Previous value: -"With a stock source: the Pexels photo or video (search_stock with seconds) to use instead of the director's pick"New value: +"With a stock source: the stock photo or video (search_stock with seconds) to use instead of the director's pick"
  5. Changed1 schema field changed
    • changedInput schema / properties / feature_artist / description
      Previous value: -"Whether the Canvas shows the artist (AI sources; needs artist photos for \"always\")"New value: +"Whether the Canvas shows the artist: auto (the director decides), always or never (AI sources; needs artist photos for \"always\")"
  6. Changed1 schema field changed
    • addedInput schema / properties / stock_id
      Added value: +{
      +  "description": "With a stock source: the Pexels photo or video (search_stock with seconds) to use instead of the director's pick",
      +  "pattern": "^\\d{1,20}$",
      +  "type": "string"
      +}
  7. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (non-readOnly, idempotent, open-world), it discloses that the call spends credits, returns video ids immediately while rendering is asynchronous, requires polling, and surfaces specific 402 error codes with the get_account fields to verify first. It does not describe what happens if the reused quote_id's payload differs from the quote, which is the main residual risk.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is short and front-loads purpose, credits cost and preconditions, but the first two sentences run together without punctuation, producing run-on, hard-to-parse text. Every sentence does carry information, so the issue is structure rather than padding.

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 15-parameter, nested-object, no-output-schema mutation tool, it covers the lifecycle (quote → create → poll get_video), cost, prerequisites and error codes, which is the information an agent cannot get elsewhere. Parameter-level detail is deferred entirely to the schema, which is acceptable at full coverage.

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 description coverage is 100% and every parameter is already documented in the schema, so the description only reinforces the quote_id consistency requirement ('request must be identical'). It adds no meaning for style, source, variations, performer or the stock/direction interplay, but the schema carries those adequately.

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?

The opening clause names the verb and resource ('Make the Canvas') and ties it to a prior quote, so an agent can tell it apart from quote_canvas and the other create_* tools. The grammar is broken ('Make the Canvas a quote priced'), which slightly obscures that this is a create-from-quote operation rather than a pricing call.

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?

It gives concrete routing: send the identical request as the quote plus its quote_id, then poll get_video until completed, and check get_account for plan.active and storage. The preconditions (active plan, room in storage) and their 402 failure modes act as explicit when-not guidance, though no other creation sibling is named as an alternative.

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