Skip to main content
Glama
tuitamogamer-gpt

youtube-mcp-server

List My Videos

youtube_list_my_videos
Read-onlyIdempotent

List uploaded videos from your YouTube channel. Paginate through results and get video metadata including title, description, and thumbnail.

Instructions

List videos uploaded to the authenticated channel.

Fetches the channel's uploads playlist ID via channels.list(mine=true), then pages through playlistItems.list to return video metadata.

Args

  • maxResults (integer 1–50, default 25): number of items per page

  • pageToken (string, optional): cursor token returned in a previous response

  • response_format: "markdown" (default) or "json"

Returns JSON shape:

{
  "items": [
    {
      "videoId": "abc123",
      "title": "My Video",
      "description": "...",
      "publishedAt": "2024-01-01T00:00:00Z",
      "thumbnailUrl": "https://..."
    }
  ],
  "nextPageToken": "CAUQAA",
  "totalResults": 42
}

Examples

  • List first 10 videos: { "maxResults": 10 }

  • Get next page: { "maxResults": 10, "pageToken": "CAUQAA" }

Errors

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

  • 404: channel has no uploads playlist (newly created channel?)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxResultsNoNumber of videos to return per page (1–50, default 25).
pageTokenNoPagination cursor from a previous response's nextPageToken.
response_formatNoOutput format: "markdown" (default) or "json".markdown
Behavior5/5

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

Annotations already indicate readOnlyHint=true and idempotentHint=true. The description adds significant behavioral details: it explains the internal process (fetches uploads playlist ID, pages through playlistItems), provides the exact JSON return shape, lists possible errors (401/403, 404), and gives usage examples. 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 sections (Args, Returns, Examples, Errors) and front-loaded with the core purpose. Every sentence adds value, no fluff. It is appropriately sized for the tool's complexity.

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?

The tool has 3 parameters, no output schema, but the description provides a full JSON shape for the return value, lists error conditions, and includes examples. Combined with annotations, this is complete and leaves no ambiguity for an AI agent.

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?

Schema coverage is 100%, but the description adds substantial meaning: it explains maxResults as 'items per page', pageToken as 'cursor token', and response_format options. It also provides default values and examples for parameter usage. This goes beyond the schema's own descriptions.

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 'List videos uploaded to the authenticated channel,' indicating a specific verb (list) and resource (videos of the authenticated user). It distinguishes from siblings like youtube_search (which searches all videos) and youtube_get_video (single video).

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 context that this tool fetches the user's own uploads via channel list and playlistItems. It includes examples and error handling, but does not explicitly state when to use it over alternatives like youtube_search or youtube_list_playlist_items. Still, the purpose is clear enough.

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