Skip to main content
Glama

create_playlist

Create new playlist inside video wprkspace

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": "create_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoPlaylist title
descriptionNoPlaylist description
workspace_idNoGumlet video workspace ID. Preferred over deprecated `collection_id` / `source_id` (same ID).
collection_idNoDeprecated. Use `workspace_id` instead. Still accepted for backwards compatibility.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / collection_id / description
      Previous value: -"Workspace ID in which the playlist should be created"New value: +"Deprecated. Use `workspace_id` instead. Still accepted for backwards compatibility."
    • addedInput schema / properties / workspace_id
      Added value: +{
      +  "description": "Gumlet video workspace ID. Preferred over deprecated `collection_id` / `source_id` (same ID).",
      +  "examples": [
      +    "646df1c9173a4a2fcac180b4"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the mutation profile is known without the description. The description adds nothing beyond that: it does not say whether duplicate titles produce separate playlists, whether an empty playlist is valid, or what permissions are needed to create one in a workspace.

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?

It is a single front-loaded sentence with no filler, which suits a simple create tool. However, its brevity slides into under-specification and it contains a spelling error, so the terseness does not fully earn its place.

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?

The tool has an output schema and complete parameter descriptions, and annotations cover the safety profile, so the description does not need to explain return values or side effects. Still, for a creation tool with all-optional parameters it should clarify that a playlist can be created with no title and what the required workspace scoping is.

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%, including the note that workspace_id supersedes the deprecated collection_id, so the schema already carries full parameter meaning. The description contributes no additional parameter context, which makes the baseline 3 appropriate.

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 uses a specific verb and resource ("Create new playlist") and states where it lives ("inside video workspace"), so an agent can tell it apart from update_playlist or delete_playlist. It stops short of differentiating from adjacent creators like create_folder or add_asset_playlist, and the misspelling "wprkspace" slightly blurs the scoping statement.

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 guidance on when to call this versus add_asset_playlist, create_folder, or update_playlist, and no statement of prerequisites or exclusions. The agent must infer the entire usage decision from the tool name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources