Vee3

youtube.video_details

Fetch metadata for a public YouTube video by video id or URL.

Accepts a bare 11-character video id (for example PuQFESk0BrA) or common YouTube watch, youtu.be, Shorts, and embed URLs. Returns title, description, view count, duration, publish date, channel id, category, keywords, and thumbnails.

Cost = 10 tokens.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`video_id`	Yes	YouTube video id or URL (for example PuQFESk0BrA, https://youtu.be/PuQFESk0BrA, or https://www.youtube.com/watch?v=PuQFESk0BrA).

Output Schema

TableJSON Schema

Name	Required	Description
`type`	No	Video type (for example NORMAL).
`title`	No	Video title.
`author`	No	Channel display name.
`category`	No	Primary category label.
`keywords`	No	Video keyword tags.
`video_id`	No	Canonical YouTube video id.
`channel_id`	No	Uploader channel id.
`thumbnails`	No	Available thumbnail images at different sizes.
`description`	No	Plain-text video description.
`video_length`	No	Video duration in seconds as a string.
`published_time`	No	Publish date (ISO 8601).
`is_live_content`	No	Whether the video is live content (True or False as a string).
`number_of_views`	No	Total view count.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedJun 21, 2026

removedOutput schema / $defs / YoutubeVideoDetailsResponseKeywordsItem

Removed value: -{
-  "additionalProperties": true,
-  "properties": {
-    "keyword": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "Single keyword tag.",
-      "title": "Keyword"
-    }
-  },
-  "title": "YoutubeVideoDetailsResponseKeywordsItem",
-  "type": "object"
-}

changedOutput schema / properties / keywords / anyOf

Previous value: -[
-  {
-    "items": {
-      "$ref": "#/$defs/YoutubeVideoDetailsResponseKeywordsItem"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

First observedJun 18, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that only public videos are supported, specifies the returned fields, and includes the token cost. It does not cover error cases or rate limits, but for a simple read-only metadata fetch, this is adequate and adds meaningful context.

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 three concise sentences, front-loaded with the core purpose, followed by input/output details and cost. Every sentence adds value with no redundancy or filler, making it an example of efficient, well-structured documentation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required parameter, no nested objects) and an output schema exists, so the description need not explain return structures. It covers input formats, public video requirement, and returned fields. Missing details like error behavior are not critical for a metadata fetch tool, and the description is complete enough for an agent to invoke correctly.

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?

The input schema already provides 100% coverage of the video_id parameter, including format examples. The description adds the explicit 'bare 11-character video id' detail and lists common URL prefixes, which slightly enhances the schema description. However, it does not fundamentally expand parameter understanding beyond what the schema already states.

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 'Fetch metadata for a public YouTube video by video id or URL', which specifies the verb, resource, and scope. It distinguishes itself from sibling tools like youtube.video_comments and youtube.channel_details by focusing on a single video's metadata, and lists the exact fields returned.

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 clearly implies when to use this tool: when you have a video ID or URL and need its metadata. It provides accepted input formats and examples. However, it does not explicitly mention alternatives or when NOT to use it, though no direct sibling tool overlaps with this functionality.

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

All Vee3 tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.