Skip to main content
Glama
gibeon-io

@gibeon/mcp-server

Official
by gibeon-io

Update playlist item

update_playlist_item

Update an existing playlist item by modifying its name, duration, schedule, asset, or other mutable fields. Only the provided fields are changed, leaving the rest intact.

Instructions

Patch an existing content item.

When to use:

  • Renaming an item, adjusting duration_seconds, changing a schedule window, swapping the asset on an image/video item.

When NOT to use:

  • For changing type — delete the item and add a new one (type drives a different validation surface).

  • For reordering — use reorder_playlist_items.

What to know:

  • Only the provided fields are touched. Pass null on nullable fields to clear them.

  • Mutable: name, duration_seconds, is_selected, schedule_start, schedule_end, asset_id, external_url, config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
configNo
item_idYes
asset_idNo
is_selectedNo
playlist_idYes
external_urlNo
schedule_endNo
schedule_startNo
duration_secondsNo
Behavior5/5

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

With no annotations provided, the description thoroughly handles behavioral disclosure. It states that only provided fields are touched, that null can clear nullable fields, and that changing type requires a delete+add, all of which are non-obvious patch semantics. This goes beyond a simple 'update' and gives the agent essential behavioral context.

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 well-structured with clear sections and concise bullet points. Every sentence adds value—no filler—and the key message ('Patch an existing content item') is front-loaded immediately.

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?

Given the tool's complexity (10 params, nested config, no output schema, no annotations), the description covers the core usage questions: when to use, when not, partial update semantics, and mutable fields. Minor gaps remain around the 'config' parameter and error/validation behavior, but the description is largely complete for safe invocation.

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?

The input schema has 0% coverage and 10 parameters, so the description must compensate. It lists all mutable fields and explains null clearing, but does not explain the opaque 'config' object or the format constraints for schedule_start/end. Parameter names are self-explanatory for most fields, but 'config' remains undefined, so only partial semantic support is provided.

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 a specific verb and resource: 'Patch an existing content item.' It clearly distinguishes this tool from siblings by using the term 'content item' and listing specific use cases like renaming or changing duration, which sets it apart from reorder and delete operations.

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 'When to use' and 'When NOT to use' sections explicitly state when this tool is appropriate and when to use alternatives such as delete+add for type changes and reorder_playlist_items for reordering. This gives the agent clear decision criteria with 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/gibeon-io/mcp-server'

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