Skip to main content
Glama

Link an artist to their released songs

link_artist
Idempotent

Set the artist’s catalog profile, once: their released songs are then listed to import Available to Artist and Label workspaces. Send catalog_artist_id from find_artist_in_catalog with catalog_confirmed=true after the user confirms they manage the selected profile. The artist names must match exactly. Also sets their Apple Music link (links.apple_music) unless one is set. Linking again replaces it; unlink with update_artist catalog_artist_id null. Then list_released_songs and import_songs.

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": {
      "artist_id": "<artist_id>",
      "catalog_artist_id": "<catalog_artist_id>"
    },
    "name": "link_artist"
  }
}

Input Schema

NameRequiredDescriptionDefault
artist_idYesThe artist id
catalog_artist_idYesTheir catalog profile id (find_artist_in_catalog)
catalog_confirmedNoSet true after the user confirms they manage the selected artist

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / catalog_confirmed
      Added value: +{
      +  "description": "Set true after the user confirms they manage the selected artist",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

With readOnlyHint=false and idempotentHint=true already declared, the description still earns credit for disclosing the Apple Music link side effect (links.apple_music, only set if absent) and that re-linking replaces the existing link. It does not explain what happens to already-linked or partially imported songs, or what errors arise from a name mismatch, so the behavioral picture is good but not complete.

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 purpose and effect, then preconditions, then follow-on tools – a logical order with no filler sentences. It is somewhat dense at five sentences, and the 'linking again replaces it' clause partially duplicates the idempotentHint annotation.

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?

Covers preconditions, side effects, replacement/unlink behavior, and the required follow-up flow, which is enough for an agent to sequence the call correctly without an output schema. Minor gaps remain around failure modes (name mismatch) and state of previously imported songs.

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% and the schema already documents catalog_artist_id's provenance (find_artist_in_catalog) and catalog_confirmed's meaning, so the description largely restates structured data. It adds only the exact-name-match requirement, which maps loosely to artist_id, making this baseline-level value.

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 – setting an artist's catalog profile link – and describes the downstream effect (released songs become listable for import). It differentiates itself from siblings by naming find_artist_in_catalog as the ID source and list_released_songs/import_songs as the follow-on tools. The opening phrase 'catalog profile, once' is slightly awkward, which keeps it just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the precondition (send catalog_artist_id from find_artist_in_catalog with catalog_confirmed=true only after the user confirms they manage the profile), the constraint (names must match exactly), and the next steps (list_released_songs then import_songs). It even names the alternative path for removal (update_artist with catalog_artist_id null).

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.

Resources