Skip to main content
Glama

Find an artist’s released songs

find_artist_in_catalog
Read-onlyIdempotent

Search the music catalog for an artist by name, to link their released songs The public music catalog (Apple Music’s; no account or login): each match with its id, name, song_count, newest_release and up to five covers of their releases (picture_url, covers), so the user can tell which profile is theirs. Search by the full name they release under (exact matches only), or pass their Apple Music artist link. Then link_artist with the id the user confirms. Only for the user’s own music: they must own or have the rights to the songs they bring in.

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": {
      "q": "<q>"
    },
    "name": "find_artist_in_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesThe artist name, or their Apple Music artist link

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the catalog is public (no account or login), matching is exact-only, and each result carries id, name, song_count, newest_release and up to five covers so the user can self-identify their profile. Annotations already cover read-only/idempotent/non-destructive, and the description supplements rather than repeats them.

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-loads the action and the key constraint, with the rights caveat and next step at the end. Minor deduction for a missing sentence break ('...link their released songs The public music catalog...'), which slightly hurts readability.

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?

With no output schema, the description compensates by enumerating the returned fields, and it covers prerequisites, matching rules, and the follow-up call. An agent has everything needed to invoke this tool and act on the result.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: q accepts either an artist name (full release name, exact match) or an Apple Music artist link, giving two distinct input modes the schema does not convey. It does not discuss the 200-character limit, but that is already documented.

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 — search the public music catalog for an artist by name — and ties it to the downstream goal of linking released songs. The sequencing note ('Then link_artist with the id the user confirms') makes the boundary with the sibling tool link_artist explicit.

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 activation conditions: use the full name the artist releases under (exact matches only) or pass an Apple Music artist link, then follow with link_artist once the user confirms an id. Also states a real prerequisite — the user must own or hold rights to the songs. It does not contrast with alternatives such as get_artist, which keeps it short of a 5.

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