Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

apple_music_track

Retrieve metadata for a specific Apple Music track using a song ID or URL, including album track links.

Instructions

apple-music: Track. GET /v1/apple-music/track. Provide one of: id, url. Get Apple Music track 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_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoApple Music song id. Some songs have standalone song URLs; for album tracks, use the url parameter.
urlNoApple Music song URL or album track URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations present, the description carries the full behavioral burden, and it does disclose a genuinely useful trait: the credit cost model, including that errors, blocked/timeout, invalid requests and cache hits are free while a success costs 1 credit. However, it says nothing about authentication requirements, response shape, rate limits, or what a successful payload contains, so the disclosure is partial rather than complete.

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 essential facts (route, inputs, cost) come first, which is good, but the pricing explanation sprawls across three sentences with a missing punctuation break ("Get Apple Music track Costs 1 credit") and repeated caveats about not-found and empty results. It is longer than the tool warrants and could be compressed to two sentences.

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-only lookup this is close to sufficient: inputs and cost are covered and no output schema exists to explain. The gaps are the absence of any statement about what the response contains or how errors surface, which matters because there are no annotations to fall back on.

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 would be 3, but the description adds a real constraint not encoded in the schema: the schema shows zero required parameters, while the description states exactly one of id or url must be supplied. That one-of relationship is meaningful routing information the agent could not infer from the structured fields alone.

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 states a specific verb and resource ("Get Apple Music track") plus the underlying route GET /v1/apple-music/track, which clearly separates it from the album and artist siblings by resource type. It stops short of explicitly naming those siblings as alternatives, so it sits just below the top mark.

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" is input guidance, not usage guidance; it never says when to call this instead of apple_music_search, apple_music_album, or apple_music_artist. There are no exclusions, prerequisites, or context about what kind of request this tool suits.

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