Skip to main content
Glama

delete_bins

Destructive

Deletes specified bins and all their contents in DaVinci Resolve, helping clean up unused media organization.

Instructions

Delete bins and everything they contain.

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": {
      "bins": "<bins>"
    },
    "name": "delete_bins"
  }
}

Input Schema

NameRequiredDescriptionDefault
binsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description does add real value by disclosing that contained items are deleted too, which annotations cannot express. It says nothing about permanence, whether confirmation or undo exists, or what the call 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?

One short sentence, front-loaded with the verb and resource, with no filler. It is efficient, though the brevity leaves gaps the agent must fill elsewhere rather than being complete.

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

Completeness2/5

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

This is a destructive batch operation with no output schema and an entirely undocumented parameter. The description should state the expected input form and at least the outcome of the call (e.g., per-bin success/failure), not just the cascade effect.

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

Parameters2/5

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

Schema description coverage is 0% for the single 'bins' parameter, and the description does not compensate: it never states whether entries are bin IDs or names, whether multiple bins are accepted, or how missing/invalid entries are handled. Only the plural noun hints at batch behavior, which is already visible in the array schema.

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 a specific verb (Delete) and resource (bins), and adds scope via 'and everything they contain'. An agent can distinguish it from move_bins or delete_clips by resource. It stops short of explicitly contrasting with siblings, which keeps it at 4 rather than 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 implied by the name and the cascade warning, but there is no explicit when-to-use or when-not-to-use guidance, and no mention of alternatives such as move_bins for relocation instead of removal. The agent must infer the context from the tool name alone.

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