AwesomeVideo

Get balance and usage

get_account

Read-onlyIdempotent

Free, read-only, needs a key. This key's spendable balance (balanceCents in credits, 1 credit = 1 cent, and as transcription seconds), the per-minute prices, and credit usage over a range (usage: per day and total, split into transcription and server burn; default the last 30 days; from and to in unix ms). response_format concise (default) returns usage totals only; detailed adds the per-day rows. Call it before a paid job or after a 402; top up with create_checkout; individual jobs are in list_jobs.

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

Input Schema

Name	Required	Description
`to`	No	End of the range, unix milliseconds. Default now.
`from`	No	Start of the range, unix milliseconds. Default 30 days ago.
`response_format`	No	concise (default): usage totals only. detailed: also per-day usage rows.

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.

AddedNov 1, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds the auth requirement ('needs a key') and cost profile ('Free'), which annotations do not convey. The default 30-day window and the concise-vs-detailed payload difference are also disclosed. Minor overlap with the readOnly hint keeps it from a 5.

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 key facts (free, read-only, needs key) and every clause carries information. The single run-on sentence with nested parentheses makes it harder to scan than it needs to be, but there is no wasted content.

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 auth, cost, default range, response_format effect, and sibling routing; an output schema exists so return-value detail is unnecessary, and the brief usage breakdown description is a bonus rather than a gap.

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 schema already documents all three parameters, but the description still adds real meaning: unix milliseconds for from/to, the 30-day default, and the credit-to-cent conversion ('1 credit = 1 cent'). That goes beyond the schema text.

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 precisely what is returned: spendable balance in cents and transcription seconds, per-minute prices, and credit usage over a date range. An agent can distinguish this from list_jobs or get_job without opening a schema.

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?

Explicit triggers ('Call it before a paid job or after a 402') plus explicit routing to alternatives ('top up with create_checkout', 'individual jobs are in list_jobs'). Nothing is left to inference.

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?