Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Apple Music album

appleMusic_album_get
Read-onlyIdempotent

Retrieve an Apple Music album using its album ID or URL to fetch album metadata for display, analysis, or catalog lookup.

Instructions

Get an Apple Music album by id or album URL. Optional inputs: albumId and url.

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "appleMusic_album_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoOptional Apple Music album URL for the request.
albumIdNoOptional Apple Music album id for the request.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

The rich annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that and notably does not clarify whether albumId and url are mutually exclusive or whether at least one is required, which matters since neither is marked required in the schema.

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?

Two short, front-loaded sentences with the identifier source stated up front. The second sentence largely repeats schema information, but there is no bloat.

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 simple read lookup with full schema coverage and complete annotations, the description is adequate but leaves one real gap: the interaction between albumId and url (must one be supplied?). No output schema exists, but the return value is not described either.

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 albumId and url are already documented in the schema; the description only restates that both are optional. Baseline 3 applies since the schema carries the parameter semantics.

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?

States a specific verb (Get) and resource (Apple Music album) plus the two lookup keys. It implicitly differentiates from siblings like appleMusic_track_get and appleMusic_artist_get, though it never names an alternative explicitly.

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 guidance on when to use this versus appleMusic_search_list or the Deezer/Spotify album tools, and no prerequisites or exclusions are given. The only usage hint is that it works by id or URL, which describes inputs rather than when to choose it.

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