Skip to main content
Glama

youtube_list_owned_videos

Read-only

List videos owned by a selected creator profile, with pagination to browse results page by page.

Instructions

List videos owned by the selected creator profile.

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": "youtube_list_owned_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageTokenNoPage token from the nextPageToken of a previous response, to fetch the next page.
maxResultsNoMaximum number of items to return, 1-50; omit to use the tool default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • addedInput schema / properties / maxResults / description
      Added value: +"Maximum number of items to return, 1-50; omit to use the tool default."
    • addedInput schema / properties / pageToken / description
      Added value: +"Page token from the nextPageToken of a previous response, to fetch the next page."
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's job is to add context — and it adds essentially none: no ordering, no indication of whether private/unlisted videos are included, no default page size, no mention of the pre-condition that a creator profile must be selected.

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?

A single front-loaded sentence with zero filler. It is efficient, though the brevity borders on under-specification for a creator-scoped listing tool.

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 two-parameter read-only list tool with full schema coverage and a readOnlyHint, the description is minimally sufficient, but it leaves the creator-profile prerequisite and result scoping implicit — details an agent would want when deciding among the many sibling list/get tools.

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?

Both parameters (pageToken, maxResults) are fully documented in the schema at 100% coverage, so baseline 3 applies. The description adds no additional meaning such as default page size or when to prefer larger maxResults.

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?

Specific verb+resource: 'List videos owned by the selected creator profile.' It is distinguishable from youtube_get_owned_video (single video) and from youtube_list_channel_videos by the ownership/creator-profile scope, but the difference from the latter is not made explicit.

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?

No when-to-use guidance, no named alternatives, no exclusions. The phrase 'selected creator profile' hints at a prerequisite (a creator profile must be selected) but never states it, and gives no cue about choosing this over youtube_list_channel_videos or youtube_creator_top_videos.

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

Deploy Server

Other Tools