Skip to main content
Glama

Set a song’s lyrics

set_song_lyrics
DestructiveIdempotent

Give a song its own lyrics, or replace them The song’s lyrics as text: plain (Suno-style [Verse]/[Chorus] tags and (x2) marks are fine), or the contents of an SRT, WebVTT or LRC file. Every word is still timed from the audio: your text fixes misheard words and sets where lines break in videos, and its section tags set the song’s sections (a chorus sung once is still a chorus). A part sung again (a chorus) can be written once; lyrics that don’t match what’s sung, or cover only part of it, are refused (409, the song unchanged). They are checked right away (analysis.lyrics in the answer says what changed), or once the analysis finishes if it hasn’t (202). Videos made from then on use them; videos already made stay as they are.

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

Input Schema

NameRequiredDescriptionDefault
lyricsYesThe lyrics: text, or an SRT, WebVTT or LRC file’s contents
song_idYesThe song id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

It discloses several behavioral traits not covered by annotations, such as the acceptance of multiple formats (SRT, WebVTT), the refusal mechanism (409), and the lifecycle rule that only new videos incorporate the change.

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 definition is highly detailed, which sacrifices brevity; however, the extensive detail is functionally necessary for the AI to understand this complex operation and its constraints.

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?

The description is exceptionally complete, covering input formats, validation logic, output behavior (new vs. old videos), and error handling, leaving no major gaps for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even with 100% schema coverage, the description adds crucial semantic value by defining the acceptable content and structure of the 'lyrics' string (text, plain, or specific file contents).

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 purpose is explicitly stated ('Give a song its own lyrics, or replace them') and is clearly distinct from related tools like clear_song_lyrics.

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?

The description provides strict usage criteria by stating that lyrics must match the audio ('lyrics that don’t match what’s sung... are refused'), which prevents incorrect invocation.

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