social-media-video-downloader

Get Video Details (Price:1-2)

get_youtube_v3_video_details

Extracts comprehensive information about a YouTube video including metadata, available formats, download links, and server-rendered video options with audio merging capabilities. Group: YouTube-Video. Billing per call: 2 Credits.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No	Language code for localized content (e.g., 'en-US', 'es'). Defaults to 'en-US'.
`fields`	No	A comma-separated list of fields to include in the response. This can be used to limit the amount of data returned. Allowed values: `contents`, `contents.videos`, `contents.audios`, `contents.images`, `contents.renderableVideos`, `contents.renderableAudios`, `metadata`, `metadata.author`, `metadata.comments`, `metadata.playlist`, `metadata.channel`, `metadata.post`, `metadata.hashtag`, `metadata.transcript`, `metadata.additionalData`. For exclusion, prefix the field with a dash; e.g. `-metadata…
`videoId`	Yes	The ID of the YouTube video.
`urlAccess`	No	When set to 'proxied', the API uses its own proxies to prevent 403 errors, which can sometimes occur with 'normal' URLs. This comes at the cost of slower download speeds. Allowed values: normal, proxied. When set to 'proxied' the request will be `billed as 2 requests`. Note: If both this parameter and `renderableFormats` are used, the total cost remains 2 requests (charges do not stack).	proxied
`countryCode`	No	ISO 3166-1 alpha-2 country code for geo-specific results (e.g., 'US', 'GB').
`getTranscript`	No	Set to true to retrieve the video transcript. Allowed values: false, true.	false
`renderableFormats`	No	A comma-separated list of quality formats to generate server-rendered video links for. If any videos are rendered, this request will be `billed as 2 requests`. Note: If both this parameter and `urlAccess='proxied'` are used, the total cost remains 2 requests (charges do not stack). The number of formats that can be rendered depends on your subscription plan. Allowed values: 144p, 144p60 HDR, 240p, 240p60 HDR, 360p, 360p60 HDR, 480p, 480p60 HDR, 720p, 720p60, 720p60 HDR, 1080p, 1080p60, 1080p60…
`transcriptLanguage`	No	The language to use for the transcript. This must be one of the languages returned in the `metadata.transcript.languages` array. If not provided, the default transcript is returned.

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the operation is extractive (read-only) and mentions 'audio merging capabilities' plus billing costs. However, it doesn't discuss rate limits, authentication requirements, or any potential side effects, which is a modest gap for a read tool.

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 concise, consisting of two sentences and a group tag. It front-loads the core purpose, then adds the group classification and billing note without any redundant phrases. Every sentence contributes useful information.

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?

Despite having 8 parameters and no output schema, the description summarizes the main return categories (metadata, formats, download links, server-rendered options). It doesn't explicitly mention transcript retrieval or transparently cover all features, but 'comprehensive information' plus the rich schema provide sufficient context for an agent to understand the tool's scope.

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 has 100% description coverage for all 8 parameters, including enums, defaults, and examples. The description itself adds no parameter-specific information beyond what the schema already provides, so the baseline of 3 is appropriate.

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 the tool 'Extracts comprehensive information about a YouTube video' and enumerates concrete outputs: metadata, formats, download links, and server-rendered video options. This specific verb+resource combination distinguishes it from sibling tools that handle posts, channels, or playlists.

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 clear context that this tool is for extracting YouTube video details, which differentiates it from channel/playlist/search tools. However, it doesn't explicitly name alternatives or explain when not to use this tool versus others, such as when a simpler search might suffice.

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

All social-media-video-downloader 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.

TDQS

B3.3/5.0

Disambiguation5/5

Every tool targets a distinct platform, resource, and action. Even the numerous YouTube search tools are clearly differentiated by their suffixes (channel, movie, playlist, video, suggestions), leaving no ambiguity.

Naming Consistency5/5

All tools follow a rigid pattern: get_{platform}_v3_{resource}_{specific}. The naming is uniformly snake_case and descriptive, making it easy to predict tool names for new resources.

Tool Count2/5

With 28 tools, the set exceeds the 25-tool threshold for being considered too many. The high granularity, especially the six YouTube search tools, could likely be consolidated without losing capability, making the tool count feel heavy.

Completeness3/5

Core download workflows are present via post details for all platforms, but there are notable gaps: Facebook, Instagram, and TikTok lack tools to list a user's posts or videos, while YouTube has full coverage including channel videos, playlists, and search. This unevenness leaves the surface feeling incomplete for non-YouTube platforms.

Resources

Need Help?