Skip to main content
Glama

Kinetune

by com.kinetune
OverviewDiscussionsAdmin

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).

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; the concept still comes from the cover
resolutionNo1080p (1080×1920) or 720p1080p
variationsNo1–4 different Canvases
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; needs artist photos for "always")auto

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. 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\")"
  3. 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"
+}
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: it is a credit-spending write, returns video ids immediately rather than the finished asset, requires polling get_video, and documents specific failure modes (402 plan_required, 402 storage_full) with the get_account fields that reveal them. The idempotency expectation (identical request to the quote) is also conveyed, complementing idempotentHint.

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?

Dense and front-loaded — the cost and the quote pairing come first, then the async flow, then preconditions. The telegraphic phrasing ('Make the Canvas a quote priced') slightly costs readability but no sentence is wasted.

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?

Given 13 params, no output schema, and an open-world mutation, the description covers cost, async result handling, and both documented error conditions, which is most of what an agent needs. The post-creation manual upload step is mentioned but the callback_url alternative path is left entirely to the schema.

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 basics are already documented; the description still adds the crucial cross-parameter constraint that the request must be identical to the quote (relevant to quote_id, metadata and callback_url). It doesn't explain variations/stock_id interplay, which the schema handles.

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 ('Make the Canvas... spends credits') and immediately separates itself from the sibling quote_canvas by requiring the same request body plus a quote_id. An agent can tell this is the paid fulfilment step of a quote/create pair.

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?

Explicit sequencing: send the identical request as the quote, add its quote_id, then poll get_video until completed, and upload in Spotify for Artists. Preconditions (active plan, storage room) and how to check them via get_account are named, though an explicit 'use quote_canvas first' pointer and mention of cancel_video/wait_for_video as alternatives is absent.

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

All Kinetune toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources