Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_get_owned_video

Read-only

Retrieve details for a video owned by the selected YouTube creator profile by passing its video ID.

Instructions

Get a video owned by the selected creator profile.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "videoId": "<videoId>"
    },
    "name": "youtube_get_owned_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoIdYesID of a video on the selected channel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • addedInput schema / properties / videoId / description
      Added value: +"ID of a video on the selected channel."
  2. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful scope by saying the video must be owned by the selected creator profile, which implies an ownership/visibility constraint, but it does not explain authorization requirements, error behavior for non-owned videos, or return format.

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 a single front-loaded sentence with no wasted wording. It delivers the core action and scope immediately.

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 simple one-parameter read tool with annotations and full schema coverage, the description is adequate but leaves gaps: it does not differentiate from the generic youtube_get_video sibling or indicate what kind of video data is returned. The missing output schema makes a brief return-value hint more valuable, though not strictly required.

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 the single videoId parameter is already documented as the ID of a video on the selected channel. The description reinforces that the video belongs to the selected creator profile, but it adds no syntax or format details beyond the schema baseline.

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?

The description states a specific verb ('Get') and resource ('a video') and scopes it to videos owned by the selected creator profile, which distinguishes it from a generic video fetch. It does not explicitly name the sibling tool it differs from, such as youtube_get_video or youtube_list_owned_videos, so it stops short of full sibling differentiation.

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?

The description implies use when retrieving an owned video for the selected creator profile, but it gives no explicit guidance on when to choose this tool versus youtube_get_video or youtube_list_owned_videos. There are no exclusions, prerequisites, or alternative-tool references.

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