Skip to main content
Glama

youtube_preflight_reorder_playlist_item

Destructive

Preview reordering a YouTube playlist item before making changes. Provide the playlist ID, item ID, and new zero-based position to verify the move.

Instructions

Read and preview reordering an immutable playlist item.

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": {
      "playlistId": "<playlistId>",
      "playlistItemId": "<playlistItemId>",
      "position": "<position>"
    },
    "name": "youtube_preflight_reorder_playlist_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
positionYesNew zero-based position of the item in the playlist.
playlistIdYesYouTube playlist ID, e.g. PLxxxxxxxxxxxxxxxx.
playlistItemIdYesPlaylist item ID (not the video ID), from youtube_list_playlist_items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.1
    • addedInput schema / properties / playlistId / description
      Added value: +"YouTube playlist ID, e.g. PLxxxxxxxxxxxxxxxx."
    • addedInput schema / properties / playlistItemId / description
      Added value: +"Playlist item ID (not the video ID), from youtube_list_playlist_items."
    • addedInput schema / properties / position / description
      Added value: +"New zero-based position of the item in the playlist."
  2. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations give only destructiveHint=true, so the description must clarify whether this call actually mutates the playlist. Instead it says 'Read and preview', which is ambiguous about side effects, and it discloses nothing about what the preview returns, whether the position is validated, or what the agent should do with the result. The 'immutable' claim is also unexplained.

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?

A single eight-word sentence with no waste and the key verb front-loaded, but it is under-specified rather than concise — the brevity comes at the cost of the usage and side-effect information an agent needs.

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?

For a three-parameter tool with no output schema and only a single destructiveHint annotation, the description should explain the preview's return value and the follow-up execute step. Neither is present, leaving the agent unable to know what a successful preflight yields.

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% and each parameter carries a clear description (position is zero-based, playlistItemId is not the video ID, playlistId format). The description adds nothing beyond the schema, so the baseline of 3 applies.

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

Purpose3/5

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

The description states a verb and resource ('preview reordering ... playlist item'), which tells an agent this is the dry-run counterpart to youtube_reorder_playlist_item. However, it never names that sibling, and the qualifier 'immutable playlist item' is unexplained and adds ambiguity rather than precision.

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 statement of when to use this preflight versus calling youtube_reorder_playlist_item directly, no mention of a validate-then-execute workflow, and no prerequisites or exclusions. The agent must infer the preflight pattern 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.

Deploy Server

Other Tools