Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Apple Music track

appleMusic_track_get
Read-onlyIdempotent

Retrieve detailed metadata for an Apple Music track using its ID or song URL. Use it to look up a specific song when building music search, playback, or catalog features.

Instructions

Get an Apple Music track by id or track URL. Optional inputs: trackId 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_track_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoOptional Apple Music song URL for the request.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
trackIdNoOptional Apple Music song id for the request.
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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it doesn't say what happens with an invalid or region-restricted id, what precedence applies if both trackId and url are passed, or what the response contains.

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 sentences and the retrieval mode is front-loaded. The second sentence largely duplicates what the first already conveyed and what the schema already labels, so it is near-redundant but not harmful.

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 tool with rich annotations and a fully documented schema this is close to adequate, but the schema marks both trackId and url as optional with no requirement that one be present, and the description never closes that gap. An agent could plausibly invoke it with neither identifier.

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 the baseline is 3. The description merely restates that trackId and url are optional inputs without adding format hints, precedence rules, or the fact that at least one is functionally required, so it contributes no meaning beyond the schema.

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 and resource ("Get an Apple Music track") plus the two addressing methods (id or track URL), which is enough to separate it from album_get and artist_get siblings. It stops short of explicitly naming which sibling to use for other entity types.

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

Usage Guidelines3/5

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

"By id or track URL" implies the two calling modes but never states that one of the two must be supplied, nor which to prefer when both are available. No when-not-to-use guidance or redirection to search_list when the id is unknown.

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