Skip to main content
Glama

render_jobs

Manage the DaVinci Resolve render queue by listing jobs, deleting a specific job, clearing all jobs, or stopping the current render.

Instructions

Render queue management. action: list | delete (job_id) | clear (all) | stop (current render).

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_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNolist
job_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose destructive scope ('clear (all)') and that 'stop' affects the current render, which is genuinely useful behavioral context. However, it says nothing about irreversibility, whether stopping discards progress, required permissions, or what 'list' returns.

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 fragments, front-loaded with the resource then the action menu. Nothing is wasted, though the telegraphic style leaves the action semantics slightly compressed.

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 annotations, no output schema, and 0% schema description coverage, the description does the minimum: it defines the operations but not their results, side effects, or confirmation requirements. For a destructive queue-management tool, that leaves noticeable gaps.

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

Parameters4/5

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

Schema description coverage is 0% and the action property has no enum, so the description is the only place the four valid action values appear — that is real added meaning. It also ties job_id to the delete action via the '(job_id)' annotation. It stops short of stating that job_id is optional/ignored for other actions.

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 description names the resource (render queue) and enumerates the four concrete operations (list, delete, clear, stop), so an agent can tell this is queue administration rather than rendering itself. 'Management' alone would be vague, but the action list rescues it. It does not explicitly differentiate from siblings like render_status or render_start, keeping it at 4.

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 through the action enumeration: delete needs a job_id, clear wipes everything, stop targets the current render. There is no statement of when to pick this over render_status for inspecting jobs, nor any precondition or caution about destructive actions.

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