Skip to main content
Glama

render_animation

Render a selected frame range of a Blender animation to an output path, enabling AI clients to generate animation files and visually verify 3D work.

Instructions

Render an animation range.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "render_animation"
  }
}

Input Schema

NameRequiredDescriptionDefault
frame_endNo
frame_startNo
output_pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the entire behavioral burden and discloses almost nothing. It does not say whether rendering is blocking, how long it takes, where output is written, or whether it overwrites existing files; an output schema exists but only covers return values, not execution semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

A single short sentence with no padding, but the brevity reflects under-specification rather than efficiency; nothing is front-loaded because there is nothing else to load.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter render operation with no annotations, the definition leaves too much unknown: how the optional frame range defaults are treated, what output_path overrides, and how the result is retrieved. Only the existence of an output schema offsets part of the gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for all three parameters, so the description must compensate and does not. "Range" loosely hints at frame_start/frame_end, but output_path is entirely unexplained, as are default behavior when frames are null.

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

Purpose3/5

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

"Render an animation range" gives a specific verb and resource, so the action itself is understandable. However, it does not distinguish this from sibling render tools such as render_preview, render_final, or render_scene; the only differentiator is the word "animation" in the resource name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to choose this over render_preview, render_final, or create_animation_preview. No mention of prerequisites, frame range defaults, or whether it must follow set_animation_range.

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

Deploy Server

Other Tools