Skip to main content
Glama
tuitamogamer-gpt

youtube-mcp-server

Get My Channel

youtube_get_my_channel
Read-onlyIdempotent

Retrieve complete details for your own YouTube channel, including statistics, branding, and settings. Returns a markdown summary or raw JSON.

Instructions

Retrieve full details for the authenticated user's own YouTube channel.

Args:

  • response_format (optional): "markdown" (default) for a concise human-readable summary or "json" for the raw API payload.

Returns (JSON shape):

{
  "id": "UCxxxxxxxx",
  "snippet": { "title", "description", "customUrl", "publishedAt", "country", "defaultLanguage", "thumbnails" },
  "statistics": { "subscriberCount", "videoCount", "viewCount", "commentCount" },
  "status": { "privacyStatus", "madeForKids", ... },
  "brandingSettings": { "channel": { "title", "description", "keywords", "country", "defaultLanguage", "unsubscribedTrailer" } },
  "contentDetails": { "relatedPlaylists": { "uploads", "watchHistory", "watchLater" } },
  "topicDetails": { "topicCategories": [...] }
}

Examples:

  • "Show me my channel info" → call with no arguments.

  • "Give me the full JSON for my channel" → pass response_format: "json".

Errors:

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

  • 404: no YouTube channel associated with this Google account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
response_formatNoOutput format: "markdown" (default) for a human-readable summary, "json" for the raw API object.markdown
Behavior5/5

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

Annotations already imply safety (readOnlyHint, idempotent). The description adds explicit error codes (401/403, 404) and detailed return schema, providing rich behavioral context well beyond 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?

Compact, well-organized sections (Args, Returns, Examples, Errors). No wasted words; every sentence adds value. Front-loaded with the primary purpose.

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?

Despite no output schema, the description fully documents the return shape with a JSON block, error handling, and usage examples. An agent has complete information to invoke the tool correctly.

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 coverage is 100% (one parameter fully described). The description adds usage examples and context ('markdown' vs 'json'), providing value beyond the schema's enum and default.

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 'Retrieve full details for the authenticated user's own YouTube channel,' specifying both the verb (retrieve) and the resource (own channel). This distinguishes it from sibling 'youtube_get_channel' which gets other users' channels.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool vs alternatives like 'youtube_get_channel.' The description only states what it does, without context on when not to use it or which sibling to prefer.

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