Skip to main content
Glama

delete_song

DestructiveIdempotent

Free but PERMANENT: deletes one song and its audio files from the user's library (frees storage; share links stop working). Only call when the user explicitly asked to delete this specific song.

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

Input Schema

NameRequiredDescriptionDefault
idYesSong id (songs[].id), not the generationId of a whole batch: each song is deleted separately.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's added value is the consequence detail: operation is free but PERMANENT, storage is freed, and existing share links stop working. Those downstream effects go meaningfully beyond the boolean flags. It stops short of a 5 because it does not say whether any confirmation step exists, what happens to already-broken links, or what the call returns on success versus a stale id.

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?

A single front-loaded sentence that leads with the cost/irreversibility signal ('Free but PERMANENT') before the effect and the usage guardrail. Every clause carries information; nothing is redundant with the schema or annotations.

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 one-parameter destructive tool with annotated destructive/idempotent hints and no output schema, the definition covers the critical unknowns: irreversibility, the files affected, collateral effects on share links, and the consent precondition. Nothing an agent needs to decide whether to call it is missing.

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 description coverage is 100% and the schema itself disambiguates the id ('Song id (songs[].id), not the generationId of a whole batch'). The description adds no parameter-level meaning beyond that, so the baseline 3 applies rather than a bonus.

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?

Specific verb+resource: 'deletes one song and its audio files from the user's library.' It scopes the operation to a single song and explicitly states the blast radius (audio files removed), so an agent can distinguish it from non-destructive siblings like rename_song or restyle_song without inspecting 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?

Provides an explicit negative guardrail: 'Only call when the user explicitly asked to delete this specific song.' That is a clear when-to-use condition and a when-not-to-use warning against proactive deletion. No alternative tool is named, but no sibling in the catalog performs deletion, so there is nothing to route to; this falls just short of a 5.

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.