Skip to main content
Glama

delete_render_jobs

Destructive

Delete render jobs by ID or remove all jobs to clear the DaVinci Resolve render queue and manage rendering tasks.

Instructions

Delete render jobs by id, or all of them.

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

Input Schema

NameRequiredDescriptionDefault
allNo
job_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare this as destructive and not read-only, so the safety profile is covered. The description adds useful scope information by saying deletion can target all jobs, but it does not clarify irreversibility, whether running jobs are affected, required permissions, or what happens with invalid IDs.

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?

The definition is a single front-loaded sentence with no redundant wording. It conveys the core action and both modes efficiently.

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?

For a simple two-parameter destructive tool with annotations covering the safety profile, the description is minimally adequate. However, it omits important operational context such as permanence and behavior when deleting all jobs, which is significant for a destructive bulk-capable operation.

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 description coverage is 0%, so the description must carry parameter meaning. It does map the two concepts: IDs for targeted deletion and 'all' for bulk deletion, but it does not explain precedence if both are provided or confirm that job_ids is optional.

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 states a specific verb and resource: delete render jobs. It also clarifies the two deletion modes, by id or all, though it does not explicitly differentiate this tool from nearby alternatives such as stop_render.

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?

The description implies that callers choose either targeted IDs or all jobs, but it gives no explicit when-to-use guidance, prerequisites, or warnings about choosing this over stopping a render. No exclusions or alternative tools are named.

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