Skip to main content
Glama

rename_song

Idempotent

Free. Rename one of the user's completed songs (title 1-80 chars). Also updates its public share page.

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": {
      "id": "<id>",
      "title": "<title>"
    },
    "name": "rename_song"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSong id (songs[].id from get_generation / list_songs).
titleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover idempotency and non-destructiveness, and the description adds two things they don't: the operation is free (no credits) and it has a side effect on the song's public share page. It stops short of saying whether the share link/slug changes or whether recipients are affected, which is the main behavioral question an agent would have before mutating a shared song.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero filler, with cost and scope front-loaded and the share-page side effect stated immediately after. Nothing could be removed without losing 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 simple two-required-parameter mutation with no output schema, the description covers cost, eligibility, and the notable side effect, which is close to sufficient. The remaining gap is whether the public share URL changes on rename, plus the return shape, which the absence of an output schema leaves entirely implicit.

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

Parameters3/5

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

Schema coverage is 50%: `id` is documented in the schema itself, while `title` carries only min/maxLength. The description's "title 1-80 chars" merely repeats the schema constraints and adds no new meaning, though "completed songs" does narrow which ids are valid. Baseline 3 is appropriate given the schema already handles the parameters.

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?

"Rename one of the user's completed songs" names a precise verb and resource, and no sibling tool performs renaming, so it is unambiguous against delete_song, restyle_song, extend_song, etc. The parenthetical length rule and the note that the public share page is also updated add scope detail rather than restating the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "completed songs" implies a precondition (the song must already be generated) and "Free" signals no credit consumption, which is useful decision input. However, there is no explicit when-to-use guidance, no statement of what to do instead for other cases, and no mention of alternatives.

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.