Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Spotify album

spotify_album_get
Read-onlyIdempotent

Fetch a Spotify album's details using its album ID or Spotify URL to retrieve release metadata for the specified album.

Instructions

Get a Spotify 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": "spotify_album_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoOptional Spotify album URL for the request.
albumIdNoOptional Spotify 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

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, openWorldHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — no mention of auth requirements, rate limits, error behavior for a bad id/URL, or what happens when both or neither identifier is given. 'Get' merely restates the operation the annotations already characterize.

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, front-loaded with the operation and resource; nothing is padded. The second sentence largely duplicates the schema's 'optional' descriptions, which is the only minor waste.

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

Completeness2/5

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

With five parameters (two of them meta-parameters the agent must supply) and no output schema, the definition should say more about how the album is identified and what comes back. It never explains what happens if neither albumId nor url is provided, despite both being optional in the schema. For a lookup tool whose whole contract is identifier handling, this is under-specified.

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 coverage is 100%, so the schema already documents albumId, url, context, llm_model and conversation_id, and the baseline of 3 applies. The description only restates that albumId and url are optional, adding no semantics such as format expectations, mutual exclusivity, or precedence — which is a meaningful gap given both identifiers are non-required.

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 a Spotify album' — and adds the identification methods ('by id or album URL'), which lets an agent distinguish it from spotify_artist_get or spotify_track_get without opening the schema. It stops short of a 5 because it never explicitly contrasts itself with the sibling album tools (appleMusic_album_get, deezer_album_get), though the provider name does most of that work.

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 when-to-use guidance, no statement about when to prefer albumId versus url, and no note on precedence if both are supplied. The description also omits that neither identifier is schema-required, leaving the agent to infer how to invoke the tool correctly.

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