@jam-jam/convert-mcp

Get one notebook playlist and its songs

jj_get_playlist

Retrieves a notebook playlist by ID with its songs in order, paginated by cursor; deleted songs are skipped.

Instructions

Returns one playlist of the calling account's notebook with its songs in summary form, in playlist order, paginated by the same opaque cursor. A song the playlist still references but that has since been deleted from the notebook is simply skipped.

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": {
      "playlistId": "<playlistId>"
    },
    "name": "jj_get_playlist"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size, default 30, hard cap 100 (25 when fields="full").
`cursor`	No	Opaque cursor from a previous call's `nextCursor`. Replay it verbatim; never build one.
`playlistId`	Yes	Stable playlist id ("pl_..."), as returned by jj_list_playlists.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.2Nov 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that songs come back in summary form, in playlist order, paginated by the same opaque cursor, and that references to deleted songs are silently skipped. It stops short of stating auth requirements or what happens when the playlistId is unknown.

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 sentences, both load-bearing, with the return shape and ordering stated before the pagination and deletion-edge-case details. Nothing is repeated from the schema and nothing is wasted.

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 three-parameter read tool with no output schema and no annotations, the description covers the important unknowns: result granularity ('summary form'), ordering, pagination mechanics, and the deleted-song edge case. Only error behavior for an invalid or inaccessible playlistId is left unspecified.

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%, so the schema already documents limit, cursor, and playlistId, including the cap and the 'replay verbatim' rule. The description only reinforces the cursor's opaque, continuation-based nature; it adds no format or constraint detail beyond the schema.

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?

States a specific verb and resource: returns one playlist of the calling account's notebook together with its songs. The singular 'one playlist' plus the required playlistId makes it distinguishable from jj_list_playlists, though no sibling is named explicitly.

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?

Usage is implied rather than stated: you fetch a single playlist by id and page through it with a cursor. There is no explicit when-to-use/when-not-to-use guidance and no named alternative for listing or searching playlists, so the agent must infer the routing.

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