Skip to main content
Glama

youtube_reorder_playlist_item

Destructive

Reorders a YouTube playlist item to a new zero-based position after an approved preview, requiring an approval ID to execute the change.

Instructions

Reorder an item after an approved preview.

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>",
      "approvalId": "<approvalId>"
    },
    "name": "youtube_reorder_playlist_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to execute; set it only after youtube_approve approved this exact preview.
positionYesNew zero-based position of the item in the playlist.
approvalIdYesApproval ID from the youtube_preflight_reorder_playlist_item preview, after approving it with youtube_approve.
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. Changed5 schema fields changedv0.3.1
    • addedInput schema / properties / approvalId / description
      Added value: +"Approval ID from the youtube_preflight_reorder_playlist_item preview, after approving it with youtube_approve."
    • addedInput schema / properties / confirm / description
      Added value: +"Must be true to execute; set it only after youtube_approve approved this exact preview."
    • 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

B3.4/5.0
Behavior3/5

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

The annotations already flag destructiveHint=true, so the agent knows this mutates state. The description adds a useful safety context — that execution is gated on an approved preview — but says nothing about side effects such as how other items are re-indexed, whether the operation is reversible, or that 'confirm' must be true. With annotations carrying the safety profile, this is adequate but not rich.

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?

One sentence, zero waste, and the approval prerequisite is front-loaded. It is slightly too terse for a destructive, five-parameter mutation tool, but there is no filler or redundancy to penalize.

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?

For a destructive write tool with no output schema, the description leans almost entirely on the schema to explain the approval/confirm gate and the position semantics. An agent reading only the description would know what it does and that a preview is required, but not the failure modes (missing confirm, stale approvalId). Minimum viable given the rich schema.

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%, so all five parameters (including the confirm flag and approvalId provenance) are already documented in the schema. The description adds no parameter-level meaning beyond 'item' and 'position' being implied, so the baseline 3 applies.

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?

States a specific verb ('Reorder') and resource ('an item' in a playlist), which is distinguishable from siblings like youtube_add_playlist_item or youtube_update_playlist. The clause 'after an approved preview' hints at the preflight/commit pairing but never names youtube_preflight_reorder_playlist_item, so the sibling differentiation is implicit rather than explicit.

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

Usage Guidelines3/5

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

The phrase 'after an approved preview' conveys the workflow prerequisite (preview → approve → execute), which is real usage guidance. However, it does not state when to choose this tool over the preflight variant, nor does it warn that calling without an approval will fail; that guidance lives only in the schema parameter descriptions.

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