Skip to main content
Glama
tuitamogamer-gpt

youtube-mcp-server

List Channel Sections

youtube_list_channel_sections
Read-onlyIdempotent

Retrieve all sections on your YouTube channel home page, such as featured playlists and popular uploads. Choose between markdown table or JSON output.

Instructions

List all sections on the authenticated user's YouTube channel home page (e.g. Featured Playlists, Single Playlist, Popular Uploads, etc.).

Args:

  • response_format (optional): "markdown" (default) for a readable table or "json" for the full API payload array.

Returns (JSON shape):

[
  {
    "id": "CS_ID",
    "snippet": {
      "type": "singlePlaylist",
      "title": "Section title",
      "position": 0,
      "channelId": "UCxxxxxxxx"
    },
    "contentDetails": {
      "playlists": ["PLxxxxxxxx"],
      "channels": []
    }
  }
]

Examples:

  • "What sections are on my channel page?" → call with no arguments.

  • "Give me the raw JSON of my channel sections" → pass response_format: "json".

Errors:

  • 401 / 403: credentials expired or missing scope — re-run npm run auth.

  • 404: authenticated account has no YouTube channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
response_formatNoOutput format: "markdown" (default) for a readable list, "json" for the raw API array.markdown
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds significant behavioral context: explains the return shape, response_format options, and common errors. No contradiction with annotations.

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 well-structured with clear sections (Args, Returns, Examples, Errors). It is concise, using bullet points and a JSON example, with no redundant information.

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?

Given the low complexity (1 optional param) and the presence of comprehensive annotations, the description is complete. It covers return values via the JSON shape, error handling, and usage examples. No output schema is needed because the JSON shape is provided.

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

Parameters5/5

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

The single parameter (response_format) is fully documented in the schema (100% coverage). The description enriches it by explaining the default and the difference between 'markdown' (readable table) and 'json' (raw API array), going beyond the enum values.

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 clearly states the tool lists all sections on the authenticated user's YouTube channel home page, with examples of section types. This distinguishes it from sibling list tools like youtube_list_playlists or youtube_list_subscriptions by specifying the unique resource.

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 provides examples of when to call the tool and includes an Errors section with troubleshooting steps (e.g., re-running auth). However, it does not explicitly state when not to use this tool or mention alternative tools for similar tasks.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tuitamogamer-gpt/youtube-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server