Revid

Export video

export_video

Export an mp4 for an existing Revid project, with the export modal's resolution, frame rate and compression settings. The call waits up to 40 seconds. An export done by then returns status "ready" with its videoUrl. A longer render (most videos over a minute, 4k) returns status "processing" with an exportId: call get_export_status with it until ready or failed. Do not call export_video again for the same project while it is processing: every call charges a new export. Requires an active Revid plan.

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": {
      "pid": "<pid>"
    },
    "name": "export_video"
  }
}

Input Schema

Name	Required	Description
`pid`	Yes	Existing Revid project id.
`fileName`	No	Optional export filename. `.mp4` is added automatically if missing.
`frameRate`	No	Frames per second: 30 (default) or 60.
`resolution`	No	Export resolution. 4k costs 10 extra credits. Omit to keep the project's own (720p by default).
`compression`	No	low (default, sharpest), medium or high (lightest file), or a CRF from 0 to 51.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`error`	No
`method`	Yes
`status`	Yes
`endpoint`	Yes
`retryAfterSeconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations (non-read-only, non-idempotent, non-destructive), the description discloses the 40-second blocking ceiling, the two possible terminal states with their payloads ("ready" with videoUrl, "processing" with exportId), the per-call credit charge, and the plan requirement. These are exactly the operational traits an agent cannot get from the structured fields.

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?

Five sentences, each carrying distinct load-bearing information in a logical order: what it produces, how long it blocks, what each outcome looks like, how to poll, and the re-call cost trap. No restatement of the title or name.

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?

For a non-idempotent, credit-charging, long-running export with an output schema, the description covers the timing model, result branching, follow-up tool, and billing constraint. An agent can invoke and handle the response correctly from this text alone.

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 100%, so every parameter including the 4k credit surcharge and CRF range is already documented in the schema. The description only gestures at the setting categories without adding syntax, defaults, or edge-case behavior beyond it, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb and resource ("Export an mp4 for an existing Revid project") plus the settings that shape the output (resolution, frame rate, compression). It does not, however, distinguish itself from the sibling `render_video`, which an agent could plausibly confuse with this tool.

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?

It states the precise follow-up path when the wait expires ("call `get_export_status` with it until ready or failed") and names an explicit prohibition with the cost rationale ("Do not call export_video again for the same project while it is processing: every call charges a new export"). The prerequisite "Requires an active Revid plan" is also surfaced, leaving nothing to inference.

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

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