Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

apple_music_search

Search Apple Music for songs, albums, artists, playlists, stations, music videos, or radio episodes by query and result type.

Instructions

apple-music: Search. GET /v1/apple-music/search. Search Apple Music Costs 1 credit when it succeeds. Costs 0 credits when sections is empty. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "query": "<query>"
    },
    "name": "apple_music_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoResult type to return. Use all, song, album, artist, playlist, station, music_video, or radio_episode.
queryYesSearch query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose a genuinely useful behavioral trait: the credit cost model, including that failures, timeouts, invalid requests and cache hits are free. It says nothing about authentication, rate limits, result ordering, pagination, or whether repeat queries return cached/stale data — all material for a search tool.

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

Conciseness3/5

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

The purpose is front-loaded, but the first line repeats "Search" three times and nearly half the text is verbose billing boilerplate about what is and isn't charged. That cost paragraph could be one short sentence without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter search with no output schema and no annotations, the essential facts are present: what it searches, the parameters, and the cost profile. What is missing is return-shape information and how the type filter interacts with results, which an agent would need to interpret 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 coverage is 100%, so both parameters (query, type) are already fully documented, including the valid values for type in the schema. The description adds no meaning beyond the schema — it never mentions query syntax, matching behavior, or default for type.

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?

"Search Apple Music" gives a specific verb and resource, and the GET path plus "sections" language confirm it is a catalog search endpoint. It stops short of distinguishing this from the sibling lookup tools (apple_music_album, apple_music_artist, apple_music_track), so an agent must infer that this one takes a free-text query.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus the sibling apple_music_album/artist/track lookups or the many other *_search tools. The only 'when' guidance is billing-related (when you are and aren't charged), which does not help an agent choose this tool.

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

Deploy Server

Other Tools