x402vid AI Intelligence & Channel Growth for YouTube Videos

Thumbnail Render

thumbnail_creation

Render a YouTube thumbnail from your photo + concept ($0.50 premium).

Slow call — allow up to 5 minutes. Filter rejections are never charged. Composite a photo into the thumbnail_concept layout via Muse Image. Give image_prompt directly (from thumbnail_concept) or a video_url to derive the concept first, then render. Photo is optional: omit image_b64/image_url with a video_url and the video's own thumbnail is used as the base (keeps faces, restyles the rest). Prefer image_url over image_b64 — the server downloads the bytes so agents never shuttle base64 through tool arguments.

Input Schema

TableJSON Schema

Name	Required	Description
`niche`	No	Optional niche for style targeting
`image_b64`	No	Your photo as base64 PNG/JPEG/WEBP (under ~7MB, data: prefix ok)
`image_url`	No	Photo URL for server-side download (preferred for large photos)
`video_url`	No	Optional video to derive the concept from first (watch, shorts, live, youtu.be all accepted; e.g. https://www.youtube.com/shorts/dQw4w9WgXcQ)
`x_payment`	No	Base64 x402 payment payload (required — pass the X-PAYMENT value as an argument over MCP)
`image_prompt`	No	Render prompt from thumbnail_concept (or omit + give video_url)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 9, 2026

changedInput schema / properties / video_url / description

Previous value: -"Optional video to derive the concept from first"New value: +"Optional video to derive the concept from first (watch, shorts, live, youtu.be all accepted; e.g. https://www.youtube.com/shorts/dQw4w9WgXcQ)"

Changed2 schema fields changedSep 6, 2026

changedInput schema / properties / image_b64 / description

Previous value: -"Your photo as base64 PNG/JPEG (under ~7MB, data: prefix ok)"New value: +"Your photo as base64 PNG/JPEG/WEBP (under ~7MB, data: prefix ok)"

addedInput schema / properties / image_url

Added value: +{
+  "default": "",
+  "description": "Photo URL for server-side download (preferred for large photos)",
+  "type": "string"
+}

AddedSep 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Adds valuable behavioral context beyond annotations: cost ($0.50), slow call up to 5 minutes, filter rejections not charged, server-side download rationale, and the use of Muse Image. No contradiction with annotations.

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?

Front-loaded with purpose and cost, then moves into latency, charging policy, and parameter guidance. Every sentence carries operational information; there is no filler.

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

Completeness5/5

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

Covers cost, latency, payment, input alternatives, optionality, and transport preference. Since an output schema exists, return-value details are not needed. The only implicit point is that one of image_prompt/video_url must be supplied, but the alternatives make that clear.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds relational meaning between image_prompt/video_url and image_b64/image_url, including the optional-photo behavior. This goes beyond what the schema alone provides.

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 (render) and resource (YouTube thumbnail), and distinguishes itself from thumbnail_concept by describing the compositing step and the two input paths. An agent can tell it apart from sibling tools without opening their schemas.

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 clear input-mode guidance: pass image_prompt directly from thumbnail_concept or use video_url to derive the concept first, and photo is optional. It also advises preferring image_url over image_b64. However, it never explicitly says when not to use this tool or names an alternative for concept-only work.

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

All x402vid AI Intelligence & Channel Growth for YouTube Videos tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?