Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_archive_video

Destructive

Archive an approved owned private YouTube video after preview approval, with explicit confirmation and reversible metadata updates.

Instructions

Archive an approved owned video (private, not scheduled; reversible via youtube_update_metadata). Approve the preview with youtube_approve, then call with confirm: true.

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": {
      "videoId": "<videoId>",
      "approvalId": "<approvalId>"
    },
    "name": "youtube_archive_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to execute; set it only after youtube_approve approved this exact preview.
videoIdYesID of an owned video to archive.
approvalIdYesApproval ID from the youtube_preflight_archive_video preview, after approving it with youtube_approve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.1
    • addedInput schema / properties / approvalId / description
      Added value: +"Approval ID from the youtube_preflight_archive_video 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 / videoId / description
      Added value: +"ID of an owned video to archive."
  2. Addedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, and the description adds valuable context: the video becomes private and unscheduled, the action is reversible via youtube_update_metadata, and execution requires a specific approval path plus confirm: true. It does not detail downstream effects on playlists or comments, keeping it just short of full transparency.

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?

It is a compact, front-loaded statement with no filler. The critical workflow and constraint information appears in the first sentence, with the required approval step immediately following.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with no output schema, the description covers the key safety context: prerequisites, state change, reversibility, and confirmation. Minor details such as return behavior or edge cases around playlist membership are absent but not essential for correct invocation.

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 three parameters are already documented in detail. The description reinforces the workflow around confirm and approvalId, but adds no parameter syntax or constraints beyond what the schema provides.

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 states a specific verb and resource ('Archive an approved owned video') and adds scoping constraints ('private, not scheduled; reversible via youtube_update_metadata'). It is clearly distinguishable from related tools like youtube_preflight_archive_video and youtube_update_metadata through the approval workflow.

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

Usage Guidelines5/5

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

It gives an explicit sequence: approve the preview with youtube_approve, then call with confirm: true. The scoping conditions ('approved owned video', 'private, not scheduled') also imply when this tool is appropriate versus prerequisites that are not met.

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