Skip to main content
Glama

set_current_bin

Sets a specified bin as the current media pool folder so imports and new timelines are placed there.

Instructions

Make a bin the current media pool folder (where imports and new timelines land).

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": {
      "bin": "<bin>"
    },
    "name": "set_current_bin"
  }
}

Input Schema

NameRequiredDescriptionDefault
binYes

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?

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real value by defining the side effect (future imports and new timelines go here), but says nothing about persistence, whether the prior current bin is unset, or permission requirements.

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?

One sentence with the action front-loaded and the clarifying parenthetical immediately after; nothing extraneous.

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?

The tool is simple (one param, no output schema, no nesting), so not much is required, but the unresolved bin-identifier format and the absence of any persistence or failure-mode note leave an agent guessing at invocation details.

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%, so the single 'bin' parameter is documented nowhere. The description never says whether the bin is identified by name, path, or index, nor what happens if the name is ambiguous — a meaningful gap for a required parameter.

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 gives a specific verb+resource ('Make a bin the current media pool folder') and the parenthetical explains what 'current' actually controls (import targets and new timeline placement). It doesn't explicitly contrast with set_current_timeline, but the bin-vs-timeline distinction is legible.

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 via the parenthetical about imports and new timelines landing in the bin; there is no explicit 'use this when...' statement and no mention of alternatives such as set_current_timeline. An agent can infer when it matters, but must do the work itself.

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