Skip to main content
Glama

Quote a Canvas

quote_canvas
Read-onlyIdempotent

The exact credits for a Spotify Canvas, before anything is charged Returns quote_id, credits and a breakdown. Always quote first and tell the user the credits before creating; credits are reserved at creation and charged only when the video is delivered.

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>"
    },
    "name": "quote_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
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

A4.2/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent read, so the description's job is to add context — and it does: nothing is charged at quote time, credits are reserved at creation and only charged on delivery. The return payload is described since there is no output schema. It omits quote expiry or whether a quote can be reused across differing parameters.

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?

Three short sentences with the purpose and cost model front-loaded; no filler. There is a punctuation defect where 'before anything is charged' runs into 'Returns quote_id', slightly hurting readability but not substance.

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 14-parameter tool with no output schema, the description covers what it does, what it returns, the billing lifecycle and the required ordering relative to creation — everything an agent needs to call it correctly. Remaining detail is fully carried by the rich schema.

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%, so every one of the 14 parameters is already documented, including enums, ranges and defaults. The description adds no parameter-level meaning beyond the schema; the only cross-parameter hint (matching metadata/callback values) lives in the schema itself. Baseline 3 applies.

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?

States a specific verb and resource — pricing a Spotify Canvas — and names the exact outputs (quote_id, credits, breakdown). The resource word 'Canvas' distinguishes it from the sibling quote tools for covers, lyric videos and music videos without needing to name them.

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?

Gives an explicit rule: 'Always quote first and tell the user the credits before creating', which tells the agent both the ordering and the user-facing obligation. It does not name create_canvas or spell out when to skip quoting (e.g. re-quote after changing parameters), so it stops just short of full when/when-not guidance.

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