AwesomeVideo

Estimate price and limits (free)

estimate

Read-onlyIdempotent

Free, never charges, works without a key. Without steps: the credits one operation would cost (operation caption, transcribe, burn, preview, translate, shorts, trim, dub or preview {mode:'sample'}) from durationSeconds, or from mediaUrl/fileId with a key; e.g. {operation: "caption", durationSeconds: 8} = 2 credits, the hosted sample. With steps: prices a whole pipeline of 1-10 steps, checks every limit before you pay (limitViolations with a fix for each), suggests free alternatives and, with a key, says whether the balance covers it. 1 credit = 1 cent. Call it before any paid tool when the cost matters; to run the job you need a key (create_key, free).

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": "estimate"
  }
}

Input Schema

Name	Required	Description	Default
`steps`	No	Ordered pipeline, 1-10 steps: [{op: caption\|transcribe\|translate\|burn\|shorts\|trim\|preview\|dub\|preview {mode:'sample'}, ...op options}].
`fileId`	No	Uploaded file id; its duration is read when durationSeconds is not given (needs a key).
`source`	No	What you know about the input: {durationSeconds, bytes, via: url\|upload, transcriptCues, mediaUrl}. Used to price and check limits.
`mediaUrl`	No	Public media link; its duration is probed when durationSeconds is not given (needs a key).
`operation`	No	Default caption (caption_video).	caption
`sourceUrl`	No	Same as mediaUrl (the caption_video name).
`voiceTier`	No	dub only.
`translateTo`	No	caption only: include translation in the price.
`hasTranscript`	No	true when you already have a transcript (subtitles or transcriptionJobId): transcription is not priced.
`hasTranslation`	No	true when you already have the translated captions: translation is not priced.
`targetLanguage`	No	dub only. Checked against the supported voices.
`durationSeconds`	No	Media length in seconds. Enough on its own: no key or media needed.

Output Schema

Name	Required	Description
`total`	No	Total number of items (paginated lists).
`result`	No	The value, when the tool returns something other than an object.
`hasMore`	No	true when more items are available (paginated lists).
`nextCursor`	No	Pass as cursor for the next page (paginated lists).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 9, 2026

addedInput schema / properties / operation / default
```
Added value: +"caption"
```

changedInput schema / properties / operation / description

Previous value: -"What to price: caption (one-call caption_video), transcribe, burn, preview, translate, shorts, trim, dub or preview {mode:'sample'} (always 0)."New value: +"Default caption (caption_video)."

addedInput schema / properties / sourceUrl

Added value: +{
+  "description": "Same as mediaUrl (the caption_video name).",
+  "type": "string"
+}

AddedNov 1, 2026

TDQS

A4.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description still adds real value beyond them: it never charges, some paths (mediaUrl/fileId probing) require a key, and it returns limitViolations with a fix per violation plus free alternatives and a balance check. However, the precise distinction between the free no-key path and the keyed path is stated in a compressed run-on way that an agent could misread.

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 two facts that matter most (free, no key needed) before the mode breakdown, and the key call-to-action is placed last. It is dense but not padded; the only drag is the repeated 'preview {mode:'sample'}' enumeration and some parenthetical clutter that makes the no-key vs keyed distinction harder to scan.

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 both invocation modes, the key requirement per mode, credit-to-cent conversion, the sort of limit feedback returned, and the recommended call ordering before paid tools. With an output schema present and 100% schema coverage, nothing an agent needs in order to call this correctly is missing.

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 goes further by tying parameters to outcomes: durationSeconds alone suffices with no key or media, fileId/mediaUrl duration is probed only with a key, steps accepts a 1-10 ordered pipeline, and it anchors pricing with the 8-second caption = 2 credits example and '1 credit = 1 cent'. That is meaning beyond the schema's field descriptions.

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 (estimate) and resource (price and limits) and immediately splits the tool's two modes: single-operation pricing versus whole-pipeline pricing via steps. The operation enumeration and the concrete example make the scope unambiguous relative to paid siblings like caption_video or burn_captions.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('Call it before any paid tool when the cost matters') and names the prerequisite/alternative path ('to run the job you need a key (create_key, free)'). An agent knows both when to call it and what to do next when it lacks a key.

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?