Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

apple_music_artist

Fetch Apple Music artist details by ID or URL to identify artists and access their profile data through the Fetchproof MCP Server.

Instructions

apple-music: Artist. GET /v1/apple-music/artist. Provide one of: id, url. Get Apple Music artist Costs 1 credit when it succeeds. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "apple_music_artist"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoApple Music artist ID. Provide id or url.
urlNoApple Music artist URL. Provide id or url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose a real behavioral trait: the credit cost model (1 credit on success; free for errors, blocked, timed-out, invalid, and cached responses; not-found charged only where published). What it omits is authentication expectations and the shape of a successful artist response.

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?

The identifying information comes first and the parameter constraint follows, which is well ordered. The billing sentences are long and somewhat boilerplate-heavy for a simple lookup, costing some efficiency.

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 read lookup with no output schema, the description is nearly sufficient, but it says nothing about what an artist record contains or whether authentication is required, leaving the agent to discover this on first call.

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%, so both parameters are already documented as 'Artist ID' and 'Artist URL'. The description restates the either/or constraint ('Provide one of: id, url') but adds no format, precedence, or fallback detail beyond the schema, so baseline 3 applies.

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?

The description gives a specific verb and resource ('Get Apple Music artist') plus the underlying route GET /v1/apple-music/artist, and the service prefix distinguishes it from spotify_artist or soundcloud_artist. It stops short of explicitly contrasting this with apple_music_search, so sibling differentiation relies on the name prefix rather than stated boundaries.

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?

'Provide one of: id, url' tells the agent which inputs to supply, but there is no guidance on when to use this lookup versus searching first (apple_music_search) or when an ID is unavailable. No prerequisites, no exclusions, no alternatives are named.

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