Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Apple Music artist

appleMusic_artist_get
Read-onlyIdempotent

Retrieve Apple Music artist details by providing an artist ID or Apple Music artist URL, so you can identify and use the correct artist profile in social or web data workflows.

Instructions

Get an Apple Music artist by id or artist URL. Optional inputs: artistId 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_artist_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoOptional Apple Music artist URL for the request.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
artistIdNoOptional Apple Music artist 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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds essentially nothing beyond them: no return shape, no behavior when the id is invalid or not found, no rate-limit or auth context, and no mention of the conversation_id handshake the server requires.

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 first sentence is tight and front-loaded, which is good. The second sentence is pure duplication of the schema property names and spends the definition's limited space on information the agent already has, rather than on the missing usage and behavior detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple read-only fetch with rich annotations and full schema coverage, and no output schema, so the description does not need to explain return values. What it leaves out is selection semantics between artistId and url and behavior on failure, which are minor but real gaps for a five-parameter tool.

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 sentence 'Optional inputs: `artistId` and `url`' merely restates the schema and arguably muddies it, since calling both 'optional' without noting that at least one lookup key is needed leaves the agent to infer the constraint.

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 an Apple Music artist') and names the two lookup keys, so the intent is unambiguous. The Apple Music platform qualifier in the text plus the name prefix distinguishes it from siblings like spotify_artist_get and deezer_artist_get, though the description never explicitly compares itself to them.

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?

It says lookups work by id or URL, but gives no guidance on when to prefer one over the other, whether they are mutually exclusive or combinable, or what happens if neither is supplied. There is no statement of when to use this tool versus the search or album/track siblings.

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