Skip to main content
Glama

Upload a background

upload_background

Upload your own photo or video, or use one of your music videos, to design a New Look around Photo: JPEG, PNG or WebP, at least 720 px on the short side, up to 25 MB. Video: MP4, MOV or WebM, 4–180 seconds, at least 720 px on the short side, up to 300 MB; it becomes a seamless loop of up to 20 s. Only with the rights to use it. Or video_id: one of this workspace's delivered music videos (list_videos with type music-video and the song's song_id), copied in as a video background (no rights_confirmed needed); the answer's music_video names its song and section (trim). preview_url is a still (a photo, or a video's poster) and video_url the video itself (null for a photo), both signed for about a week. A lyric video with it must be of that song: it takes that section (send that trim, or leave trim out), and the music video plays once from its first frame in step with the lyrics, with its own sound. Then quote a lyric video with look {"mode":"new","category":"…","background":{"source":"upload-photo" or "upload-video","upload_id":"…"},"visibility":"private"}. 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

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": "upload_background"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_urlNoA public https URL of the photo or video (a file on your computer: create_upload, then its file_url)
video_idNoOne of your delivered music videos, instead of a file: it then plays in step with its song’s lyrics, with its own sound
rights_confirmedNoYou have the rights to use this photo or video (required with a file or file_url)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / file_url / description
      Previous value: -"A public https URL of the photo or video"New value: +"A public https URL of the photo or video (a file on your computer: create_upload, then its file_url)"
  2. Changed1 schema field changed
    • changedInput schema / properties / video_id / description
      Previous value: -"One of your delivered music videos, instead of a file"New value: +"One of your delivered music videos, instead of a file: it then plays in step with its song’s lyrics, with its own sound"
  3. Changed3 schema fields changed
    • changedInput schema / properties / rights_confirmed / description
      Previous value: -"You have the rights to use this photo or video"New value: +"You have the rights to use this photo or video (required with a file or file_url)"
    • addedInput schema / properties / video_id
      Added value: +{
      +  "description": "One of your delivered music videos, instead of a file",
      +  "format": "uuid",
      +  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "rights_confirmed"
      -]
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false. Beyond that, the description discloses format/size/duration limits, that a video is trimmed to a seamless loop of up to 20 s, that a music video plays once from its first frame in step with the lyrics with its own sound, that signed URLs last about a week, and the exact failure modes (402 plan_required, 402 storage_full) with the diagnostic tools to check.

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?

The content is valuable but delivered as long semicolon-chained sentences mixing input rules, return values, error codes, and downstream usage. Key constraints (formats, size, credits/no-rights path) are buried mid-paragraph rather than front-loaded, making skimming harder.

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 three-parameter mutation with no output schema, the description covers inputs, limits, prerequisites, error codes, and even the return values (preview_url as a still, video_url for video, both signed for about a week). Nothing an agent needs to call 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, but the description adds real meaning: the mutual exclusivity of file vs. video_id, that rights_confirmed is required with a file but unnecessary for video_id, and how the resulting upload_id is consumed in the look.background object with source upload-photo or upload-video.

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 (upload) and resource (background: photo, video, or a workspace music video) and frames the outcome ('to design a New Look around'). The two input paths (file vs. video_id) are spelled out so an agent can distinguish this from create_upload or list_videos.

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 routes between alternatives: use file_url for your own media (create_upload first for a local file), or video_id for a delivered music video found via list_videos with type music-video and the song's song_id, noting rights_confirmed is not needed in that case. It also states prerequisites (active plan, storage room) and the downstream step (quoting a lyric video with look.background).

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