Skip to main content
Glama

Rename a song

rename_song
DestructiveIdempotent

Change a song’s title A new title changes nothing else. instrumental is deprecated: the analysis hears whether a song has vocals. Switching it still analyzes the song again and replaces the analysis (an instrumental isn't transcribed, and its lyrics, including any set with set_song_lyrics, are deleted): poll get_song until analysis.status is "ready". Leave it out unless the user asks.

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

Input Schema

NameRequiredDescriptionDefault
titleNoThe new title
song_idYesThe song id
instrumentalNoDeprecated: the analysis hears whether a song has vocals. true: a song without vocals (never transcribed, never lip-synced). Stops working on 2027-04-30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / instrumental
      Added value: +{
      +  "deprecated": true,
      +  "description": "Deprecated: the analysis hears whether a song has vocals. true: a song without vocals (never transcribed, never lip-synced). Stops working on 2027-04-30.",
      +  "type": "boolean",
      +  "x-sunset": "2027-04-30"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "song_id",
      -  "title"
      -]New value: +[
      +  "song_id"
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by describing exactly what the destructive path destroys: the analysis is replaced, the song is not transcribed, and existing lyrics including any set with set_song_lyrics are deleted. It also explains the deprecation mechanics and the required follow-up polling, which the destructiveHint and idempotentHint flags alone would not convey.

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 largely front-loaded, with every clause carrying operational information. It is marred only by a run-on opening ("title A new title") and a parenthetical that packs several facts into one long sentence, which costs some readability.

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 rename tool with a hidden destructive side effect, the description covers the mutation scope, the deprecation path, the data loss consequences, and the correct follow-up poll. With no output schema, naming get_song and the exact readiness field is precisely the missing piece an agent would need.

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 genuine meaning beyond the schema for `instrumental`: the schema only states it is deprecated and dated, while the description explains the side effects of switching it and that the analysis re-runs. `title` and `song_id` are left entirely to the schema, which is acceptable given their full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource ("Change a song's title") and immediately scopes the effect ("A new title changes nothing else"), which distinguishes it from siblings like rename_artist or rename_look. The missing sentence break between the purpose and the next clause slightly blurs the front-loaded statement, so it falls short of a clean 5.

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 explicit conditional guidance for the optional deprecated parameter ("Leave it out unless the user asks") and tells the agent what to do after a state-changing call (poll get_song until analysis.status is "ready"). It does not name alternatives such as reanalyze_song, so it stops short of full when/when-not/alternative coverage.

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