Skip to main content
Glama
Sign In
Revel Digital MCP Server

Revel Digital MCP Server

Official
by RevelDigital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

putplaylist

Replace an existing playlist with a new configuration by providing a complete playlist object, including sources and duration.

Instructions

Put a playlist. Replaces a playlist with the one provided.

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": {
      "id": "<id>"
    },
    "name": "putplaylist"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPlaylist Id
requestBodyNoPlaylist

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.20

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so the description must carry the full burden. While 'replaces' implies mutation, there is no disclosure of side effects (e.g., overwriting all fields), permissions needed, or idempotency. The description is too brief to be transparent.

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

Conciseness4/5

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

Two short sentences, no fluff. However, it could be slightly more informative without being wordy. The structure is acceptable but borderline under-specified.

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 complexity of the input schema (nested object with many fields), the description is insufficient. It does not explain that it performs a full replacement (not merge) and that fields not provided might be cleared. Missing output schema, but not required. Agent may misunderstand the tool's behavior.

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 coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema. It does not clarify how the top-level id relates to the requestBody.id, nor does it explain the complex nested structure of the requestBody. The description is redundant with the schema.

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 that the tool replaces a playlist (update operation). The verb 'Put' combined with 'replaces a playlist with the one provided' indicates a full replacement. Distinguishes from siblings like patchplaylist (partial update) and postplaylist (create). However, it could be more explicit about using the playlist ID to target the specific playlist.

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?

No guidance on when to use this tool vs alternatives like patchplaylist (partial update) or postplaylist (create). Does not mention that it performs a full replacement and requires an existing playlist ID. Missing context on prerequisites or side effects.

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