Skip to main content
Glama
Sign In

Soundiiz

by com.soundiiz
OverviewDiscussionsAdmin

Create a Soundiiz import link from a public playlist URL

createSoundiizImportLinkFromUrl

Read a public playlist of at most 200 source items from its full HTTPS URL and create a 24-hour Soundiiz import link. Supported sources: Spotify, Apple Music, Deezer, SoundCloud, YouTube, YouTube Music, Qobuz, TIDAL and public Soundiiz playlists. Private playlists and short links are unsupported. Preserve a requested destination and omit it otherwise. Show warnings, the exact shareUrl including query parameters, and expiry. The user reviews the tracks and connects the destination to complete the transfer in Soundiiz. No music-service password or user token is needed.

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": {
      "playlistUrl": "<playlistUrl>"
    },
    "name": "createSoundiizImportLinkFromUrl"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoOptional two-letter catalog country for a TIDAL source, default US. Apple Music uses the storefront in its URL.
destinationNoInclude only when the user requests a platform. Use its documented Soundiiz API corename; otherwise omit this field.
playlistUrlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare the generic read/write, idempotency and open-world flags; the description adds the details that actually matter here: a 24-hour expiry, a 200-item ceiling, no password or user token required, and warnings plus the exact shareUrl (including query parameters) being returned. It also discloses that the tool only stages the transfer and a human must connect the destination. None of this is derivable from the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and its limit, then constraints, then the return/user-flow note. Every sentence carries information, though the source-platform roster could be compressed. The return-value sentence slightly overlaps the output schema but still reads as useful rather than filler.

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 three-parameter, open-world creation tool with an output schema, this covers preconditions (public, full URL, item cap), supported platforms, exclusions, expiry, auth requirements, and the human handoff. An agent could call it correctly without consulting the sibling list or any other context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 67% schema coverage, the description meaningfully extends the schema: playlistUrl must be the full HTTPS URL of a public playlist (not a short link) with at most 200 source items, and destination should be carried through only when the user asked for a platform. The country parameter's TIDAL catalog fallback is left to the schema, which is acceptable since the schema documents it well.

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: read a public playlist from a full HTTPS URL and create a 24-hour Soundiiz import link. The supported-source list and the 200-item cap make the scope unmistakable. It never names its closest sibling, createSoundiizImportLink, so an agent must infer the split from the URL-based framing alone.

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 concrete when-to-use and when-not-to-use guidance: private playlists and short links are unsupported, and the destination must be preserved when requested and omitted otherwise. It also notes the user must finish the transfer in Soundiiz, which frames the expected workflow. No alternative tool is named, so the routing decision against createSoundiizImportLink stays implicit.

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

All Soundiiz toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources