Skip to main content
Glama

Change a song’s cover

set_song_cover
DestructiveIdempotent

Replace a song’s cover art, or add one Adds cover art to a song without one, or replaces it. The new cover is checked like an upload’s (a square JPEG or PNG, 1000–6000 px, up to 20 MB) and kept at its full size and at 1536, 640 and 160 px; the cover before stays on the song (list_song_covers) and can be put back in use (use_cover). Videos already made keep the cover they had; quotes, Looks, Canvas loops, music video plans and videos made from then on use the new one. Refused (409, code song_busy) while a video of the song is being made: try again once it is done.

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

Input Schema

NameRequiredDescriptionDefault
song_idYesThe song id
cover_art_urlNoA public https URL of the new cover (or upload the file with the CLI)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (destructive, idempotent, open-world) the description discloses validation rules (square JPEG/PNG, 1000–6000 px, 20 MB), derived renditions kept at full size and at 1536/640/160 px, that the prior cover is retained and restorable, and precisely which downstream artifacts keep the old cover versus pick up the new one. It also documents the 409 song_busy failure mode and the retry remedy, which is exactly the operational context annotations cannot express.

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?

The body is dense and front-loads constraints, then retention behavior, then downstream effects, then the conflict case — a sensible order. It loses a point because the opening sentence is garbled and duplicated ('Replace a song's cover art, or add one Adds cover art to a song without one, or replaces it'), so the first line costs reading effort without adding information.

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 two-parameter mutation with no output schema, the definition covers the behavioral surface thoroughly: input validation, stored variants, reversibility, blast radius on other assets, and the busy conflict. What is missing is authorization context — nothing says which scope or role is needed to change a cover — and no hint of what the call returns on success.

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 already 100%, so the baseline is 3; the description adds real meaning by stating the acceptance criteria for the supplied image (format, square aspect, pixel bounds, size cap) that the schema's 'public https URL' description does not. It also notes the CLI upload path as an alternative to passing cover_art_url, tying the two parameters together.

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?

The opening states a specific verb and resource ('Replace a song's cover art, or add one') and immediately bounds the operation to two cases: adding a missing cover or replacing an existing one. It also names sibling tools (list_song_covers, use_cover) so an agent can place this tool in a workflow without opening any schema.

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 clear context for when to reach for this tool and explicitly routes cover-restoration to use_cover and cover enumeration to list_song_covers. The gap is that other cover-producing siblings (make_cover, quote_cover, redraw_cover, delete_cover) are never differentiated, so an agent must infer whether to generate a cover elsewhere and then call this, or call this first.

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