Skip to main content
Glama
fetchtranscript-mcp

fetchtranscript-mcp

Official

get_channel_info

Retrieve YouTube channel details by channel ID or @handle to identify and inspect a channel before fetching its videos or transcripts.

Instructions

Get information about a YouTube channel.

Args: channel_id: YouTube channel ID (UCxxxxxx format) or handle (@username)

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_id": "<channel_id>"
    },
    "name": "get_channel_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does little with it. It does not disclose whether the call requires authentication, how invalid IDs or missing channels are reported, or whether the operation is a safe read; an output schema exists so return values need not be explained, but the error and auth profile is entirely absent.

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?

The purpose sentence is front-loaded and the Args block is compact, with no filler wording. The docstring-style formatting is slightly heavier than needed for a single parameter but nothing is wasted.

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 one-parameter read tool with an output schema, the definition covers the essentials needed to invoke it correctly. It remains thin on routing guidance relative to a fairly populated sibling set and says nothing about failure modes or rate limits.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the schema only labels the field 'Channel Id', so the description's note that it accepts either a UCxxxxxx ID or an @username handle adds genuinely new, actionable meaning. It stops short of covering edge cases such as full URLs or malformed identifiers.

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?

The description states a specific verb and resource ('Get information about a YouTube channel'), which is unambiguous on its own. It does not distinguish the tool from siblings such as get_video_metadata or list_channel_videos, so an agent must infer the boundary from the names alone.

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 when-to-use guidance, no statement of when another tool is preferable, and no prerequisites. The only implicit cue is that this targets channels rather than videos or comments, which is derivable from the resource noun alone.

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