AwesomeVideo

Auto short clips

shorts

Idempotent

Paid: 6 credits per source minute. Pick 1-5 non-overlapping moments from a transcript, reframe each to 720x1280 (9:16), and burn captions. reframe=face (default) follows the main speaker with a smoothed crop and falls back to center when no face is found; reframe=center forces a center crop. Same price either way. platform (tiktok, instagram_reels, youtube_shorts, ...) keeps captions inside that app's safe zone at the same price; say "shorts para Reels" → platform=instagram_reels. Clip length is minSeconds (5-60, default 15) to maxSeconds (up to 60); out-of-range values return 422 limit_exceeded before any charge. Long transcripts are read in windows of 400 cues (up to 4000). 402 insufficient_balance with checkoutUrl when the balance is short.

Input Schema

Name	Required	Description
`count`	No	1-5 clips. Out of range returns limit_exceeded before any charge.
`fileId`	No
`preset`	No
`autoFit`	No	Default true: caption size, words per caption (4 on 9:16, 5 on 1:1, 7 on 16:9), and a default safe zone follow the video shape, so text reads the same at 720p and 1080p and stays clear of app UI. Pass false only when the user wants the preset's exact fixed pixel sizes. Same price.
`reframe`	No	face (default): track the main speaker. center: plain center crop. Same price.
`mediaUrl`	No
`platform`	No	Where the video will be posted: tiktok, instagram_reels, youtube_shorts, facebook_reels, snapchat_spotlight, linkedin, youtube, x (aliases like reels, instagram, shorts, snap, twitter; case-insensitive). Keeps captions out of that app's buttons and text. If the user says "para TikTok" / "for Reels", pass it; if they did not say and it matters, ask. Same price. Unknown values return 422 invalid_platform before any charge. See list_platforms.
`faceAvoid`	No	true = move captions off faces (samples faces at 2 fps, same price; result.faceAvoid.faceLayout). Shortcut for styleOverrides.faceAvoid.
`subtitles`	No
`maxCredits`	No
`maxSeconds`	No	Longest clip, minSeconds-60 seconds.
`minSeconds`	No	Shortest clip, 5-60 seconds. Default 15.
`highlightColor`	No	#RRGGBB for highlightWords. Default #FACC15.
`highlightWords`	No	Shortcut: words or phrases to color in every caption (accent/case-insensitive), e.g. ["AwesomeVideo", "gratis"]. Maps to styleOverrides.wordHighlights rule {id:"custom", words, color}. Same price.
`styleOverrides`	No	Per-call style changes deep-merged onto the preset (same fields as list_presets style; null removes a field), validated with the renderer schema and bundled fonts. Example {"fontSize":72,"maxWordsPerCaption":2,"wordEntrance":"bounce"}. Same price. No need to save_custom_preset. Every field with examples: get_style_reference.
`transcriptionJobId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A3.9/5.0

Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: pricing (6 credits per source minute), reframe fallback behavior (face → center), platform safe zones, clip length constraints with error codes (422 limit_exceeded), and balance errors with checkoutUrl (402 insufficient_balance). These details are critical for an agent to predict costs and handle failures.

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?

The description is well-structured and each sentence generally earns its place by conveying pricing, behavior, or constraints. It is slightly front-loaded with pricing rather than the core action, but overall it remains efficient and scannable.

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?

Given the tool's complexity (16 parameters, multiple options, no output schema), the description covers most essential aspects: core action, pricing, error conditions, reframe behavior, and platform handling. It omits guidance on when to use versus alternatives, but that is addressed in usage guidelines; overall it is fairly complete for correct invocation.

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 63%, so some parameters are already documented. The description adds meaning for reframe (face fallback), platform (example mapping 'shorts para Reels'), and min/max seconds (error behavior). However, it does not compensate for undocumented parameters like fileId, preset, mediaUrl, subtitles, and transcriptionJobId, leaving gaps.

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 states a specific verb and resource: 'Pick 1-5 non-overlapping moments from a transcript, reframe each to 720x1280 (9:16), and burn captions.' This clearly distinguishes the tool from siblings like burn_captions or create_clips by combining moment selection, reframing, and caption burning into a single operation.

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to use this tool versus alternatives like create_clips or burn_captions. It implies usage through phrases like 'Pick 1-5 non-overlapping moments from a transcript,' but does not name or exclude any sibling tool or state conditions for selection.

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

All AwesomeVideo 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?