ytm-runlist-mcp

Overview Schema Source Related Servers Discussions Admin

create_reordered_playlist_copy_tool

Create a new playlist copy with a custom order of tracks, using a subset of items from the source playlist without modifying the original.

Instructions

Create a new playlist copy from a proposed order.

Unlike in-place reorder, ordered_playlist_item_ids may be a subset of the source playlist.

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": {
      "source_playlist_id": "<source_playlist_id>",
      "ordered_playlist_item_ids": "<ordered_playlist_item_ids>",
      "title": "<title>"
    },
    "name": "create_reordered_playlist_copy_tool"
  }
}

Input Schema

Name	Required	Default
`title`	Yes
`description`	No
`privacy_status`	No	private
`source_playlist_id`	Yes
`ordered_playlist_item_ids`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 11, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions the subset distinction but fails to state other important aspects like creation side effects, authorization needs, or idempotency. For a creation tool, more behavioral context is needed.

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 two sentences long, front-loaded with the core action and resource. Every word is necessary, and no information is redundant.

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 has 5 parameters, an output schema, and several sibling tools, the description is too sparse. It lacks explanation of the output, required parameter relationships (e.g., source_playlist_id and ids), and potential edge cases like duplicates. The presence of output schema does not fully compensate.

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?

Schema description coverage is 0%, so the description should compensate for parameter meaning. It only clarifies 'ordered_playlist_item_ids' as a subset of source items. Other parameters like title, description, privacy_status, and source_playlist_id are left implicit, relying on names.

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 clearly states the purpose: 'Create a new playlist copy from a proposed order.' with a specific verb and resource. It also distinguishes from the sibling 'reorder_original_playlist' by noting the key difference about subset of items.

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

Usage Guidelines4/5

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

The description provides a clear context for when to use this tool versus in-place reorder by highlighting that ordered_playlist_item_ids may be a subset. However, it lacks explicit when-not-to-use guidance or mention of other alternatives.

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

Deploy Server