Skip to main content
Glama

Remove a song’s lyrics

clear_song_lyrics
DestructiveIdempotent

Go back to the transcribed words Videos made from then on show the words as transcribed.

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

Input Schema

NameRequiredDescriptionDefault
song_idYesThe song id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context that annotations cannot express: future videos will render with the auto-transcribed words. It stops short of stating whether the removed lyrics are recoverable or what precondition (an existing custom lyric set) is required.

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?

Only two short sentences, so there is no padding, but the second sentence is grammatically broken and reads as a run-on, which hurts front-loading and scanning. Brevity is not the issue; legibility is.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with no output schema and annotations covering the destructive profile, the description is close to sufficient. However, for a destructive revert it omits whether the change is reversible and what state the song must be in, which are the two things an agent most needs before invoking it.

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?

There is a single required parameter (song_id) at 100% schema coverage, so the schema fully documents it. The description never references song_id or clarify that it targets one song's lyric set, so it adds nothing beyond the schema, capping this at the baseline.

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?

The title 'Remove a song's lyrics' supplies a specific verb and resource, and the description explains the resulting state ('go back to the transcribed words'). The garbled phrasing ('Videos made from then on show the words as transcribed') weakens it, but an agent can still tell this clears custom lyrics rather than editing them.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of the obvious counterpart sibling, set_song_lyrics, which is the tool to call for the opposite operation. The agent must infer that this is the revert/undo path from the title alone.

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