Skip to main content
Glama
@jam-jam/convert-mcp

@jam-jam/convert-mcp

by titouannwtt

List songs published by an account

jj_list_profile_songs

List the songs an account has published on its profile, newest first, with cursor pagination. Use it to browse a public songbook and check which tracks expose playable audio.

Instructions

Lists the songs an account has chosen to publish on its profile, newest first, with cursor pagination. hasAudio and audioPlayable are only ever true between accounts that follow each other MUTUALLY: without that link the very existence of a backing track is withheld, and no endpoint serves audio at all. A private account you do not follow refuses the call; an unknown handle returns not-found. Consumes one unit of the daily read quota.

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": {
      "handle": "<handle>"
    },
    "name": "jj_list_profile_songs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, default 30, hard cap 100.
cursorNoOpaque cursor from a previous call's `nextCursor`. Replay it verbatim.
handleYesPublic username of the account, with or without the leading "@".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.2/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 disclosure burden and does so: it declares newest-first ordering, cursor pagination, a privacy rule (private account you don't follow refuses the call), an error case (unknown handle → not-found), a conditional field-visibility rule for hasAudio/audioPlayable gated on mutual following, and a quota cost of one daily read unit. These are exactly the non-obvious behaviors an agent cannot learn from the schema.

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?

Three sentences, each load-bearing: purpose first, then the non-obvious audio-visibility rule and failure modes, then the cost. No filler, no restatement of the tool name, and the most decision-relevant facts are front-loaded.

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 read tool with no annotations and no output schema, the definition is nearly complete: ordering, pagination, privacy failures, conditional field visibility, and quota cost are all covered. The only gap is that it never sketches the song item shape beyond naming two flags, which is the one thing an agent must infer about the response.

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% — handle format, limit default/cap, and cursor replay semantics are all already documented in the schema. The description adds only the aggregate note that results come "newest first, with cursor pagination," which restates rather than extends the per-parameter documentation, so the baseline 3 applies.

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?

"Lists the songs an account has chosen to publish on its profile" names a specific verb and a precisely scoped resource, with ordering and pagination stated up front. The phrase "chosen to publish on its profile" implicitly separates it from the owned-library listing (jj_list_songs) and the playlist listing sibling, so an agent can pick it without opening a schema.

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 description gives rich conditions around the call — private account refusal, unknown-handle not-found, mutual-follow requirement, and a one-unit quota cost — which is real operational guidance. What it never does is explicitly route the agent: it does not say to use jj_list_songs for your own library or jj_list_profile_playlists for the profile's playlists, so selection between siblings is left to inference from the name.

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