Skip to main content
Glama

YouTube Video Details & Outlier Score

youtube_video_details

Scrape metadata and stats from YouTube videos, channels, playlists or search terms to find viral outliers: views per day, engagement rate and an outlier score.

Instructions

Scrape YouTube video details and find viral outliers: views, likes, comments, subscribers, tags, chapters, views per day, engagement rate and an outlier score. Accepts video URLs or IDs, channel or playlist URLs, @handles, Shorts, or search terms. No YouTube API key and no browser. Use this for YouTube research, niche analysis, SEO and content strategy. Van Born Labs. $0.80 per 1,000 videos, billed to your Apify account.

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_video_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
videosNoWatch URLs, youtu.be links, Shorts, live or embed URLs, or bare 11-character video IDs. Playlist and channel URLs pasted here are expanded too.
channelsNoChannel URLs or @handles (latest videos; add /shorts or /streams to the URL for those tabs) and playlist URLs.
maxResultsNoHard cap on the number of videos scraped (and charged) in this run. Defaults to 5 in this MCP server to keep runs cheap.
searchTermsNoYouTube search queries. Top video results are scraped — great for finding outliers in a niche.
maxConcurrencyNoParallel requests.
maxVideosPerSourceNoHow many videos to take from each channel, playlist or search term.
proxyConfigurationNoApify Proxy (datacenter) is used by default.
residentialFallbackNoRetry blocked requests through residential proxy (no extra cost to you).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing operational constraints an agent can't see elsewhere: no API key, no browser, results billed to the Apify account at $0.80 per 1,000 videos, and maxResults defaults to 5 to keep runs cheap. It does not explain why readOnlyHint is false (results presumably land in a dataset) or what the output shape is, which leaves a gap on a non-read-only, open-world tool.

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?

Front-loaded with the core action and return fields, then input forms, then cost. Dense but nearly every clause earns its place; the 'Van Born Labs' vendor stamp is the only purely promotional fragment.

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?

With no output schema, listing the returned fields is genuinely necessary and is done well, and the eight parameters are all documented in schema. Pricing and default-cap behavior are covered; only the dataset/return delivery mechanism is unaddressed.

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 every parameter already carries its own documentation. The description usefully synthesizes the accepted input forms (URLs, IDs, @handles, Shorts, search terms) into one place, but adds no syntax or constraint detail the schema lacks, so the baseline 3 applies.

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?

States a specific verb and resource ('scrape YouTube video details') and enumerates the artifacts produced (views, likes, comments, tags, chapters, views per day, engagement rate, outlier score). This clearly separates it from youtube_comments, which handles one of those artifacts rather than the video-level record.

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?

Gives explicit positive contexts ('YouTube research, niche analysis, SEO and content strategy') and explains which input forms are accepted, which implies the tool is the entry point for video-level lookups. It never says when to prefer a different tool or what this tool should not be used for, so it stops short of full routing guidance.

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