Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

apple_music_album

Retrieve Apple Music album details by supplying an album ID or URL, enabling programmatic access to album information through Fetchproof.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
idNoApple Music album ID. Provide id or url.
urlNoApple Music album URL. Provide id or 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?

No annotations are supplied, so the description carries the full burden. It does add genuinely useful behavior: the operation is a GET (implying read-only) and the credit-cost model is spelled out, including that failures and cache hits are free. It stops short of describing authentication needs, rate limiting, or what the returned album object looks like, which matters since there is no output schema.

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 sentence is front-loaded and efficient, but the raw route "GET /v1/apple-music/album" is redundant implementation detail, and the multi-clause pricing boilerplate dominates the description even though it is generic across the API surface.

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-optional-parameter lookup tool this covers identity selection and cost, which is most of what an agent needs. With no annotations and no output schema, though, the description should say something about the album payload returned, and it does not.

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 already 100%, and both parameter descriptions already say "Provide id or url." The description reinforces the either/or exclusivity rule, so an agent cannot miss that only one identifier is needed, but it adds no format or resolution details beyond that.

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 album") and restates the route GET /v1/apple-music/album, so the agent knows exactly what it retrieves. It does not distinguish itself from near-siblings such as apple_music_search, apple_music_track, or spotify_album, leaving that differentiation to the name.

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?

The only guidance is "Provide one of: id, url," which is a parameter constraint rather than a when-to-use rule. Nothing states when to call this versus apple_music_search (to resolve a name to an ID) or the Spotify equivalent, and no prerequisites or exclusions are given.

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