Ravenpost

Check a video render

get_video

Read-onlyIdempotent

Check a render create_video or capture_screenshot started: its status (queued, rendering, ready, failed), progress and, once ready, the media ids and URLs. Reads one row; nothing is changed. Set wait (seconds, up to 45) to hold the call until it settles or the time is up — one call like that beats polling every second.

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": {
      "renderId": "<renderId>"
    },
    "name": "get_video"
  }
}

Input Schema

Name	Required	Description	Default
`wait`	No	Seconds to wait for it to finish (default 0: answer at once)
`renderId`	Yes	The id create_video or capture_screenshot returned

Output Schema

Name	Required	Description	Default
`ok`	No
`next`	No
`media`	No
`render`	No
`credits`	No
`ignored`	No
`posterUrl`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'reads one row; nothing is changed' partly restates them. Beyond that, the description adds genuine context: the enumerated status lifecycle and the fact that `wait` blocks the call up to 45 seconds rather than returning immediately.

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 sentences, front-loaded with what the tool returns, followed by the one non-obvious behavioral tip (blocking wait vs. polling). No wasted clauses.

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?

An output schema exists, yet the description still summarizes the meaningful return shape, and it names the prerequisite producing tools. For a two-parameter read tool with full annotation coverage, nothing material 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 coverage is 100% and both parameters are documented there, including the 0–45 range and default. The description reinforces the blocking behavior of `wait` and where renderId comes from, but adds little syntax or semantics the schema doesn't already carry, so the baseline 3 applies.

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 (check) and resource (a render started by create_video/capture_screenshot), and enumerates the exact return payload: status values (queued, rendering, ready, failed), progress, media ids and URLs. It is unmistakable against siblings like get_post or get_analytics.

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?

Explicitly anchors usage to a preceding create_video or capture_screenshot call and advises using the wait parameter instead of polling every second. It stops short of naming an alternative or a when-not-to-use case, so it's strong but not exhaustive.

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

All Ravenpost 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.