Skip to main content
Glama

Create bulk render

create_bulk_render

Queue multiple renders from one template, each with custom variable sets. Validates items individually, queues valid ones, and reports errors for invalid ones.

Instructions

Queue N renders from one template/payload and a list of per-item variable sets (max 500 items, plan-limited). Validation is best-effort per item: valid items queue, invalid ones are reported in itemErrors. Returns bulkId + jobIds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoWhat the payload/template rendersvideo
nameNoName for the bulk batch
itemsYesOne entry per render; each item's variables merge over the base variables.
payloadNoFull Zvid project JSON (scenes, elements, output settings). Call get_project_schema for the JSON Schema, list_supported_elements / get_element_docs for element docs, and validate_project_json BEFORE rendering.
templateNoTemplate ID, e.g. "tpl_AbC123..." (20 chars after the prefix)
overridesNoOptional output overrides applied on top of the payload/template.
variablesNoBase variables applied to every item
webhookUrlNoOptional per-job webhook URL notified on render.completed / render.failed.
Behavior3/5

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

Discloses validation is best-effort, max 500 items, plan-limited, and returns bulkId+jobIds. However, does not clarify async behavior or authentication needs.

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?

Three sentences, front-loaded with key action and limits, no fluff.

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

Completeness3/5

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

Covers core behavior and returns but does not explain template/payload choice or link to sibling tools. Adequate but not comprehensive.

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%, so description adds limited value. Mentions items are per-item variable sets and validation behavior, but these are covered by schema.

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?

Clearly states the tool queues multiple renders from a template/payload with per-item variable sets. Distinguishes from sibling create_render by focusing on bulk operation.

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

Usage Guidelines3/5

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

Implies usage for multiple renders (bulk) but does not explicitly contrast with create_render or state when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Zvid-io/zvid-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server