Framevine

Get render status

get_render_status

Read-onlyIdempotent

Check a timeline render started by render_timeline. Returns its status (QUEUED, PROCESSING, COMPLETED, FAILED or CANCELLED), progress, and the output video URL once COMPLETED.

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

Input Schema

Name	Required	Description	Default
`renderId`	Yes	Render id returned by render_timeline.
`threadId`	Yes	Thread id the render belongs to.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 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 true and destructiveHint false, so the safety profile is covered. The description adds real value beyond that: the exact status vocabulary and the fact that an output video URL appears only once COMPLETED, which tells the agent how to interpret a COMPLETED-but-empty response.

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?

A single front-loaded sentence: purpose first, then return shape and the terminal-state condition. No filler or repetition of the title.

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?

No output schema exists, so the description carries the return-value burden itself and does so by listing statuses, progress and the output URL. With annotations covering safety and schema covering both params, nothing an agent needs in order to call this 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 coverage is 100% and both parameters are described there (renderId from render_timeline, threadId scoping the render). The description adds no extra meaning about the parameters, 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?

Specific verb (check) plus resource (timeline render status), and it names the originating sibling render_timeline so the agent can place it in the workflow. The enumerated status values make the return semantics unambiguous.

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?

"Started by render_timeline" clearly establishes the precondition and the natural moment to call this tool. It stops short of explicit guidance on polling cadence or what to do on FAILED, so no full when/when-not treatment.

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

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