Spotify MCP Server and API by Cotlet

Add songs to playlist in Spotify

spotify_add_songs_to_playlist

Read-onlyIdempotent

Add songs to playlist in the user's own Spotify account from ChatGPT, Claude or any AI agent. Returns how to do it in Spotify step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Spotify Cloud Browser. Spotify's official API: Spotify has a full Web API and, since 23 Apr 2026, an official connector for Claude (checked 5 Nov 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "spotify_add_songs_to_playlist"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses the return format (step-by-step screens, buttons, fields) and explicitly says it 'opens nothing by itself,' preventing an agent from mistaking it for a write operation. It does not cover auth or rate-limit behavior, but with annotations present this is solid added context.

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 core behavior is explained in the first two sentences, but the final sentence about Spotify's official API and connector dates is extraneous and could distract an agent. The opening sentence also repeats the title before the guide-only clarification arrives.

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?

For a zero-parameter, read-only guide tool with rich annotations and no output schema, the description covers what it returns, what it does not do, and which tools to use next. The only missing piece is a clearer statement of when to prefer this over direct API or sibling options.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema cannot be enriched further; per the rubric this sets a baseline of 4. The description correctly does not invent parameter details.

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 operation and resource—adding songs to a playlist in the user's own Spotify account—and then clarifies that the tool returns step-by-step instructions rather than performing the action itself. It does not explicitly contrast with sibling Spotify tools, but the guide-only purpose is clear after the second sentence.

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?

It gives an implied workflow ('then do it with the cotlet_browser_* tools in the user's Spotify Cloud Browser'), but it never states when not to use this tool or how it compares with sibling spotify_* tools. The official API/connector sentence reads as context rather than actionable alternative guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Spotify MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?