Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

create_playlist

Create a new playlist for a user by specifying their user ID and playlist name. This tool enables playlist management through the Multi-MCPs server.

Instructions

Create a new playlist for a user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes
nameYes

Implementation Reference

  • The MCP tool handler for 'create_playlist'. Validates input arguments (user_id and name) and calls the SpotifyClient's createPlaylist method to create the playlist.
    async create_playlist(args: Record<string, unknown>) {
      if (!cfg.spotifyClientId || !cfg.spotifyClientSecret) throw new Error("SPOTIFY_CLIENT_ID/SECRET are not configured");
      const userId = String(args.user_id || "");
      const name = String(args.name || "");
      if (!userId || !name) throw new Error("user_id and name are required");
      return client.createPlaylist(userId, name);
    },
  • Registration of the 'create_playlist' tool in the Spotify API module, defining its name, description, and input schema.
    {
      name: "create_playlist",
      description: "Create a new playlist for a user",
      inputSchema: {
        type: "object",
        properties: { user_id: { type: "string" }, name: { type: "string" } },
        required: ["user_id", "name"],
      },
    },
  • Input schema definition for the 'create_playlist' tool, specifying user_id and name as required string parameters.
    inputSchema: {
      type: "object",
      properties: { user_id: { type: "string" }, name: { type: "string" } },
      required: ["user_id", "name"],
    },
  • Helper method in SpotifyClient class that makes the API call to create a playlist for the given user.
    async createPlaylist(userId: string, name: string) {
      return this.request(`/users/${userId}/playlists`, {
        method: "POST",
        headers: await this.authHeaders(),
        body: { name, public: false },
      });
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates a playlist but does not cover critical aspects like whether it requires specific permissions, if it's idempotent, what happens on failure, or any rate limits. This leaves significant gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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?

Given the tool is a mutation with 2 parameters, no annotations, and no output schema, the description is incomplete. It lacks details on behavior, parameter meanings, and expected outcomes, making it inadequate for safe and effective use by an AI agent.

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

Parameters2/5

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

The input schema has 2 parameters with 0% description coverage, and the tool description does not add any semantic information about 'user_id' or 'name' beyond what's implied by the tool name. It fails to explain what these parameters represent, such as format or constraints, leaving them undocumented.

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 clearly states the action ('Create') and resource ('new playlist for a user'), making the purpose understandable. However, it does not differentiate from sibling tools like 'add_tracks_to_playlist' or 'create_card', which would require specifying it's for music/media contexts or unique to playlist creation.

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?

The description provides no guidance on when to use this tool versus alternatives, such as 'create_card' or 'create_page', nor does it mention prerequisites like user authentication or context-specific scenarios. It lacks explicit when/when-not instructions or named alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TaylorChen/muti-mcps'

If you have feedback or need assistance with the MCP directory API, please join our Discord server