Skip to main content
Glama
Sign In
@gibeon/mcp-server

@gibeon/mcp-server

Official
by gibeon-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update playlist

update_playlist

Update a playlist's metadata by renaming it, changing its default item duration, or replacing its cover image.

Instructions

Patch a playlist's metadata.

When to use:

  • Renaming a playlist, changing its default item duration, or swapping the cover image.

When NOT to use:

  • For changing items — use add_playlist_item / update_playlist_item / delete_playlist_item.

What to know:

  • Only name, default_interval, image_uri are mutable here. Pass image_uri: null to clear the cover.

  • Updating a playlist does NOT trigger a publish on its own; a player assigned to this playlist still needs publish_players to pick up the new items list.

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": {
      "playlist_id": "<playlist_id>"
    },
    "name": "update_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
image_uriNo
playlist_idYes
default_intervalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations to rely on, the description carries the full burden. It discloses that only three fields are mutable, that image_uri:null clears the cover, and that updates do NOT trigger publish. It lacks details on error handling and auth, but covers the most consequential behaviors.

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 tightly structured with short, purposeful sections and bullet points. Every sentence adds distinct value, and the scannable layout makes it easy for an agent to extract routing and behavioral information quickly.

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 simple metadata patch with no output schema, the description provides a complete operational picture: what is mutable, null semantics, and the publish side-effect. Generic auth/error details are omitted but are typically constant across tools. The description is sufficient for correct invocation.

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?

Schema description coverage is 0%, so the description must compensate. It names the mutable fields and adds semantic meaning for image_uri (null clears) and default_interval (default item duration). The required playlist_id is self-evident from the schema, and the additional details go beyond schema types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Patch a playlist's metadata,' which is a specific verb+resource combination. It then enumerates the exact mutable fields (name, default_interval, image_uri) and distinguishes itself from item-level sibling tools, making the purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes explicit 'When to use' and 'When NOT to use' sections. It names concrete scenarios for use and directs users to add_playlist_item / update_playlist_item / delete_playlist_item for item changes, plus the publish_players caveat—exemplary routing guidance.

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