@jam-jam/convert-mcp

Delete a notebook song

jj_delete_song

Delete a song from your notebook by song ID; it leaves playlists, removes its published copy, notifies importers, and cannot be undone.

Instructions

Deletes a song from the calling account's notebook. Idempotent: deleting twice succeeds twice, and an unknown id succeeds too (saying "no such song" would leak whether it exists in someone else's notebook). Side effects are the same as deleting in the app: the song leaves all its playlists, its published copy disappears from the profile, and accounts that had imported it are notified. This cannot be undone from the API: confirm with the person before calling it.

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": {
      "songId": "<songId>"
    },
    "name": "jj_delete_song"
  }
}

Input Schema

Name	Required	Description	Default
`songId`	Yes	Stable notebook song id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.2Nov 13, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it declares idempotency, explains that unknown ids also succeed, gives the security rationale (not leaking existence in another notebook), enumerates side effects (playlist removal, published copy removed, importer notifications), and flags irreversibility.

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?

Front-loads the core action, then layers idempotency, side effects, and the confirmation warning in a tight sequence. Every sentence contributes distinct information; none is redundant padding.

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 single-parameter destructive tool with no annotations and no output schema, the description covers everything an agent needs: what happens on repeat or invalid calls, what downstream state changes, and that the operation is irreversible.

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 100% for the single songId parameter, so the baseline is 3. The description implicitly tells the agent that a nonexistent id is accepted, which adds a little meaning, but it offers no format or sourcing details beyond what the schema already states.

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?

States a specific verb and resource with scope: "Deletes a song from the calling account's notebook." The notebook/account scoping distinguishes it from sibling read or creation tools such as jj_get_song and jj_create_song without needing to open their schemas.

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 clear pre-call guidance: "confirm with the person before calling it" because the action cannot be undone from the API. It doesn't name an alternative tool, but there is no deletion alternative among the siblings, so the omission is not material.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.