Revid

Get export status

get_export_status

Read-only

Follow an export_video call that returned status "processing": pass its exportId. Waits up to waitSeconds (default 40) for the render, then returns status "ready" with the videoUrl, "failed" with the reason, or still "processing" with the render's progress (0 to 1): then call it again. Renders usually take 1 to 10 minutes; one still rendering after an hour fails with Timeout. 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": {
      "exportId": "<exportId>"
    },
    "name": "get_export_status"
  }
}

Input Schema

Name	Required	Description	Default
`exportId`	Yes	The exportId returned by `export_video`.
`waitSeconds`	No	How long to wait for the render before answering, 0 to 40. Default 40; 0 checks once.

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.9/5.0

Behavior5/5

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

Annotations only declare a safe read, so the description carries polling semantics: the blocking wait, the 1-10 minute typical render window, the progress value 0 to 1, and the one-hour timeout failure mode. It also discloses the plan requirement, an auth prerequisite annotations cannot express.

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?

Dense but front-loaded: the triggering condition comes first, then the wait semantics, then the outcome branches, then timing expectations. Every clause carries operational information with no filler.

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?

Despite an output schema existing, the description summarizes all three return branches and their payloads, covers the polling loop and timeout, and notes the plan prerequisite. Nothing an agent needs to invoke and interpret it 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% and already documents both parameters, but the description adds the causal link that exportId must come from a prior export_video call and frames waitSeconds as a blocking wait whose expiration yields a still-processing answer rather than a failure.

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 (get export status) and immediately anchors it to the export_video call that produced the exportId, so it is unmistakable against siblings like get_media_status or get_episode_status.

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?

Explicitly says when to call it (after export_video returns "processing"), what to do on each outcome (on "processing" call it again; "ready" gives videoUrl; "failed" gives a reason), and when to give up (one hour → Timeout). No inference is required.

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?