Skip to main content
Glama

render_batch

Render multiple video clips at once by submitting a list of settings; all items are validated before starting, and a batch ID tracks progress via job status.

Instructions

Many clips at once. items = a list of render settings, e.g. [{"image": "cat.png", "prompt": "...", "style": "Lively"}, ...] (same keys as render). All items are checked before any starts. Batches wait while the user's own renders go first. Over 30 minutes in total: tell the user the estimate and call again with user_confirmed=true. Returns a batch id; job_status(batch id) reports progress.

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": {
      "items": "<items>"
    },
    "name": "render_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
labelNo
priorityNobatch
user_confirmedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

The annotations show this is a non-read-only, non-destructive write, and the description adds real behavior on top: all items are validated before any job starts, batches queue behind the user's own renders, batches over 30 minutes require explicit confirmation, and the call returns a batch id to poll with job_status. These are the exact operational traits an agent needs and none of them are in the annotations.

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

Conciseness4/5

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

The definition is compact and leads with the purpose, then moves through validation, queueing, the confirmation gate, and the return value. The inline JSON example is long, but it is the only documentation of the item shape, so it earns its space. A few clauses are dense enough that a shorter list format would be easier to scan.

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

Completeness4/5

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

For a batch write tool with no output schema, the definition explains the return value and the j ob_status handoff, and it makes the confirmation rule explicit. The remaining gap is that label and priority are not defined, which matters for a tool whose behavior includes scheduling priority.

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 0%, so the description has to explain all four parameters. It covers items well, with a concrete example and a pointer to render for key names, and it explains the confirmation flow for user_confirmed. It says nothing about label or priority, so half the parameters remain unexplained.

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

Purpose4/5

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

The definition opens with the concrete action, rendering many clips at once, and ties each item back to render's schema via "same keys as render". That gives an agent enough to separate it from the single-clip render sibling, though the one-line phrasing never explicitly names render as the single-item alternative.

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?

The definition says to call again with user_confirmed=true when the total exceeds 30 minutes and to tell the user the estimate first, which is a clear conditional rule. It also points to job_status for progress. It never says how to proceed for a single clip, so the agent has to infer that render is the right tool for that case.

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