social-media-video-downloader

Search All

get_youtube_v3_search

Search across all YouTube content types (videos, channels, playlists). Group: YouTube-Search. Billing per call: 1 Credits.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No	Language code for localized content.
`query`	Yes	The search query.
`sortBy`	No	DEPRECATED: The sort order for search results. Please use 'prioritize' and 'uploadDate' instead. Allowed values: relevance, rating, upload_date, view_count.	relevance
`duration`	No	Filter results by video duration.	all
`features`	No	A comma-separated list of video features to filter by. Allowed values: 360, 3d, 4k, creative_commons, hd, hdr, live, location, purchased, subtitles, vr180.
`nextToken`	No	A token for paginating to the next set of results.
`prioritize`	No	Prioritize results by relevance or popularity.	relevance
`uploadDate`	No	Filter results by upload date.	all

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only includes operational metadata (group, billing) and does not disclose read-only nature, pagination behavior, or any limitations. The nextToken parameter hints at pagination but is not explained.

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 extremely concise and front-loaded with the core purpose in one sentence. There is no redundant information or fluff, making it easy to scan.

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?

Given the tool has 8 parameters and no output schema, the description is minimal. It does not explain result format, pagination usage, or how to filter effectively. However, the schema covers parameter details, so the description is not wholly inadequate but could provide more context for a complex search tool.

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 schema already documents all parameters effectively. The description adds no parameter-level information beyond what is in the schema, which meets the baseline for high coverage.

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 'Search across all YouTube content types' which is a specific verb (search) and resource (all YouTube content), and it distinguishes from sibling targeted search tools like search_video and search_channel.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for all content types but provides no explicit guidance on when to use this tool versus the targeted search tools (e.g., 'use search_video for only video results'). No alternatives or exclusions are mentioned.

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?