Skip to main content
Glama

add_render_job

Queues a render job for a chosen or current timeline using current Deliver settings and returns the job ID.

Instructions

Add a render job for a timeline (current by default) with the current Deliver settings. Returns its job id.

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": "add_render_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
timelineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description's main added value is that the job inherits the 'current Deliver settings' and that it returns a job id. It does not say whether the job begins rendering immediately, whether existing queued jobs are affected, or whether permissions/state are required. Useful but incomplete above the annotation baseline.

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?

Two short sentences with the action front-loaded and the return value stated second; no filler. It is close to minimal, though it could trade a few words for the missing immediate-start clarification.

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?

With no output schema, the description correctly discloses the return ('its job id') and the settings source, and it explains the lone parameter's default. However, for a job-creating mutation it omits whether rendering starts or must be triggered separately and any failure/precondition behavior, leaving a real gap for correct invocation.

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% and the single parameter's schema is ambiguous (string|integer|null, titled 'Timeline', default null). The description partially compensates by saying the timeline defaults to 'current', explaining both meaning and default. It does not clarify whether the value is a name, index, or id despite the anyOf allowing both string and integer.

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?

States a specific verb+resource: 'Add a render job'. It also states the settings source ('with the current Deliver settings'), which sharpens what the tool actually creates. It does not distinguish itself from the related start_render or set_render_settings siblings, so it falls short of a 5.

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?

Usage is only implied by the verb 'Add' — the agent can infer it creates a queued job rather than starting one. There is no explicit guidance on when to use this instead of start_render, nor on prerequisites such as render settings already being configured. The '(current by default)' note is the only contextual hint.

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