Skip to main content
Glama
Sign In

YouTube Transcript + YouTube Search MCP

by com.getyoutubetranscript
OverviewDiscussionsAdmin

List Channel Posts

list_channel_posts
Read-only

Use this when the user wants a YouTube channel's community posts: announcements, polls and updates a creator posts outside of videos. Returns each post's text, links, likes, comments and attached image, one page at a time. Pass continuation from a previous response for the next page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_channel_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNoChannel @handle, URL, or UC... id. Required unless `continuation` is set.
continuationNoOpaque token from a previous response - fetches the next page.

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 cover the safety profile (readOnly, non-destructive, open-world). The description adds real behavioral context the annotations don't: the returned fields (text, links, likes, comments, attached image) and that results are paginated one page at a time. Auth requirements and rate limits remain undisclosed, keeping it below a 5.

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?

Three tight sentences: purpose first, then what is returned, then how to paginate. Every sentence earns its place with no preamble or 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?

With only two optional parameters, no output schema, and annotations covering safety, the description supplies the missing return-shape and pagination details an agent needs to invoke and iterate correctly. Nothing material is left out.

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 both parameters are already documented in the schema. The description's note about passing `continuation` for the next page essentially restates the schema's 'Opaque token from a previous response' and adds no new syntax or constraints. Baseline 3 applies.

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 (list) and resource (YouTube channel community posts) and scopes it with concrete examples (announcements, polls, updates outside of videos), which cleanly separates it from siblings like list_channel_videos and search_channel_videos. An agent can select it without opening the 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?

Explicitly says 'Use this when the user wants a YouTube channel's community posts' and adds a continuation procedure for paging. It does not name an alternative tool or state when-not to use it, so it falls short of the top band, but the triggering condition is unambiguous.

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