Skip to main content
Glama
Sign In

Panda Video

by com.pandavideo
OverviewDiscussionsAdmin

Move Videos Between Folders

panda_action_move_videos_by_folder
DestructiveIdempotent

Deterministically resolve a source and target folder and move every video from the source into the target in one call. Pass target_folder_ref='root' to move to the root (no folder). Skips videos already being deleted. Free action (no credits). dry_run=true (default) returns a preview of which videos would move.

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": {
      "source_folder_ref": "<source_folder_ref>",
      "target_folder_ref": "<target_folder_ref>"
    },
    "name": "panda_action_move_videos_by_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNotrue = preview only; false = move
idempotency_keyNoReserved client-supplied key to make retries safe (not yet enforced server-side)
source_folder_refYesSource folder name, ID, or dashboard URL
target_folder_refYesTarget folder name, ID, or dashboard URL — or 'root' to move to the root (no folder)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructive/idempotent/openWorld, but the description adds genuinely non-obvious behavior: 'Skips videos already being deleted', 'Free action (no credits)', and that dry_run=true yields a preview of which videos would move. It does not cover permissions or what happens to the now-empty source folder.

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?

Four short sentences, front-loaded with the core action, then the 'root' special case, skip behavior, cost, and the dry_run default. Efficient, though the dry_run preview sentence partially duplicates the schema default.

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

Completeness4/5

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

For a destructive mutation with no output schema, the description compensates by explaining the dry_run preview output and the no-credit cost, and annotations cover the safety profile. Missing only auth/permission expectations and the fate of the emptied source folder.

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 100%, so all four parameters are already documented (including target_folder_ref='root' and dry_run's preview semantics), and the description largely restates those. Baseline 3 applies since the schema carries the load.

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 (move) and resource (every video in a source folder) with an explicit scope ('every video from the source into the target in one call'), which implicitly separates it from the per-video sibling panda_move_videos. It never names an alternative sibling explicitly, so it stops 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: the bulk folder-level framing plus the 'root' target hint tell the agent this is the folder-wide move, but there is no explicit when-to-use/when-not or comparison against panda_move_videos or panda_action_delete_folder_videos. Adequate but with clear gaps.

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

All Panda Video toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources