Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Spotify track

spotify_track_get
Read-onlyIdempotent

Retrieve a Spotify track's details by track ID or URL. Use it to look up metadata for a specific song when you already have its identifier or link.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
urlNoOptional Spotify track URL for the request.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
trackIdNoOptional Spotify track 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, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only the two identification modes and nothing about rate limits, auth requirements, or error behavior when a track is not found.

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 core action, with no filler. The second sentence is somewhat redundant with the schema's own 'Optional' descriptions.

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-only lookup with no output schema, the description covers the essentials but omits what the response contains and how the tool behaves when neither or both lookup keys are given. The bookkeeping parameters (context, llm_model, conversation_id) are adequately explained in the schema itself.

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 schema already documents all five parameters, and the baseline is 3. The description restates that `trackId` and `url` are optional but does not clarify mutual exclusivity or precedence, so it adds little 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?

The description names a specific verb and resource ('Get a Spotify track') and states the two lookup keys, which distinguishes it from sibling track tools on other platforms like appleMusic_track_get and deezer_track_get. It stops short of contrasting with Spotify siblings or explaining lookup precedence.

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 what happens when both `trackId` and `url` are supplied, and no indication of which key is preferred. The agent is left to infer that this is a simple single-track lookup with no alternatives.

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