TopxAI Videos

Generate a video

generate_video

Submit a text-to-video job. Billed per second of the requested length plus a $0.01 call fee when the provider accepts the job; a job that fails is refunded. Poll video_status with the returned request_id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>"
    },
    "name": "generate_video"
  }
}

Input Schema

Name	Required	Description	Default
`model`	No	Video model.
`prompt`	Yes	What happens in the clip.
`duration`	No	Clip length in seconds.
`resolution`	No		480p
`aspect_ratio`	No	Optional aspect ratio such as 16:9 or 9:16.

Output Schema

Name	Required	Description
`error`	No	Present on a failed call: category (client, wallet, topxai, upstream, budget), message, charged, charged_usd.
`model`	No
`status`	No
`charged`	No	Whether the wallet was debited for this call.
`duration`	No
`request_id`	No	The job id to poll with video_status.
`resolution`	No
`charged_usd`	No	The recorded wallet debit in USD, model price and call fee included.
`call_fee_usd`	No
`billing_request_id`	No	The relay request id of the charge.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does real work: it discloses billing (per second of requested length plus a $0.01 call fee), the refund condition for failed jobs, and the asynchronous submit-then-poll flow. It omits auth requirements, rate/concurrency limits, and typical latency, which keeps it below 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: the action first, then cost/refund and the polling instruction. Every clause carries decision-relevant information with no padding.

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?

An output schema exists, so return values needn't be explained, and the description still supplies the cost model, failure refund, and next-step polling. Minor gaps remain around job latency and provider rejection behavior, but nothing an agent needs in order to call it correctly is missing.

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 80%, so the schema already documents prompt, duration, model, and aspect_ratio. The description only gestures at 'requested length' (duration) and never explains model or resolution choices, so it adds little meaning beyond the schema — baseline 3.

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 ('Submit a text-to-video job') and implicitly scopes it as the creation half of an async pair, naming video_status as the follow-up. An agent can tell this apart from the sibling without opening either schema.

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 follow-up routing: 'Poll video_status with the returned request_id,' which is the key usage pattern for an async job tool. It doesn't state when not to use it (e.g., editing an existing job or re-polling), so it falls short of full when/when-not guidance.

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

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