Skip to main content
Glama
Sign In
YouTube Channel MCP

YouTube Channel MCP

by joinhackyard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Draft translated titles and descriptions

translate_video_metadata
Read-only

Drafts video titles and descriptions in other languages so your videos reach viewers who search in those languages. Returns drafts for approval before applying localizations.

Instructions

Drafts the video's title and description in other languages so it can reach viewers who search in them. Returns drafts only; apply them with set_video_localizations after the user approves.

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": {
      "video_id": "<video_id>",
      "languages": "<languages>"
    },
    "name": "translate_video_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNoWhich connected channel: channel ID (UC...), @handle or name. Omit to use the default channel.
video_idYes
languagesYesBCP-47 codes, e.g. ["hi", "es", "pt-BR"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description reinforces the non-persistent behavior by stating 'Returns drafts only' and requiring approval before applying. It adds real value beyond the annotations, though it omits cost/quota implications and whether existing metadata is the translation source.

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?

Two sentences, front-loaded with the action and its purpose, followed by the critical constraint that output is drafts only. No filler, no restatement of the title or name.

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 an AI-backed operation with no output schema, the description leaves useful things unsaid: what a draft set looks like (one title plus one description per language?), whether translation is derived from existing metadata, and any quota or latency expectation. The read-only contract and the follow-up tool are covered, so it is adequate but not complete.

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 67%, with channel and languages documented in the schema but video_id left bare. The description adds no parameter-level meaning at all — no note on the 20-language cap, whether BCP-47 codes are required, or whether the source language matters. Baseline 3 is appropriate when the schema carries most of the load.

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?

States a specific verb and resource: 'Drafts the video's title and description in other languages,' plus the goal (reach viewers who search in those languages). It also names the sibling it hands off to (set_video_localizations), so an agent can separate drafting from applying without opening either schema.

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 establishes the workflow explicitly: this tool produces drafts, and set_video_localizations is what persists them after user approval. It gives clear context for use but no exclusions, e.g. it never says when to prefer generate_metadata or whether this should be run before or after SEO review.

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