Skip to main content
Glama
Sign In

YouTube Transcript + YouTube Search MCP

by com.getyoutubetranscript
OverviewDiscussionsAdmin

Get Channel Banner

get_channel_banner
Read-only

Use this when the user wants a YouTube channel's banner or profile picture, for example to download the artwork or check how a channel presents itself. Accepts an @handle, channel URL, or UC... ID. Returns the uncropped banner URL, every crop size YouTube serves, and the avatar; has_banner is false when the channel has none.

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": {
      "channel": "<channel>"
    },
    "name": "get_channel_banner"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYesChannel @handle, URL, or UC... id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral detail beyond annotations: accepted input forms, the return contents including uncropped banner and crop sizes, and the has_banner=false edge case when no banner exists.

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 front-loaded with the use case, followed by input formats and return values. It is compact and every sentence contributes useful information without redundancy.

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

Completeness5/5

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

For a one-parameter, read-only tool with no output schema, the description is complete: it explains when to use it, what inputs are accepted, what is returned, and the no-banner edge case. Nothing essential for correct invocation is missing.

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%, and the single channel parameter is already documented as accepting an @handle, URL, or UC... id. The description repeats those accepted formats but adds no new syntax or constraints beyond the schema, so baseline 3 is appropriate.

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 goal: retrieving a YouTube channel's banner or profile picture. It clearly distinguishes this from sibling tools that list videos, playlists, posts, or transcripts, and it names the exact resources returned (banner crops and avatar).

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?

It gives a clear when-to-use condition: when the user wants channel artwork or wants to inspect how a channel presents itself. It does not name explicit alternatives or when-not-to-use cases, but the sibling tools are sufficiently different that this is a minor omission.

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

All YouTube Transcript + YouTube Search MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources