Skip to main content
Glama
Sign In

Panda Video

by com.pandavideo
OverviewDiscussionsAdmin

Duplicate Folder Videos

panda_action_duplicate_folder_videos

Deterministically resolve a folder and create a copy of every CONVERTED video inside it. Duplication only works for non-external, non-funnel videos (the API rejects others, surfaced per-video). dry_run=true (default) previews the affected videos.

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": {
      "folder_ref": "<folder_ref>"
    },
    "name": "panda_action_duplicate_folder_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNotrue = preview only; false = duplicate
folder_refYesFolder name, ID, or dashboard URL
idempotency_keyNoReserved client-supplied retry key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already disclose the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=true), so the bar is lower. The description adds distinctive behavior: only CONVERTED/non-external/non-funnel videos duplicate, failures are surfaced per-video rather than aborting, and dry_run previews. It omits cost/credit implications and says nothing about the non-idempotent retry behavior implied by idempotency_key.

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?

Three tight sentences, front-loaded with the action and scope, followed by eligibility constraints and the dry_run default. No filler.

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 non-idempotent bulk mutation with no output schema, the description covers resolution, eligibility filters, per-video error surfacing, and the preview default, which is enough to call it correctly. Minor gaps remain around credit cost and the idempotency_key retry contract.

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 coverage is 100%, so the schema already documents folder_ref, dry_run, and idempotency_key. The description reinforces deterministic folder resolution and the dry_run default but adds no syntax or format detail, and never explains idempotency_key. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (duplicate/copy) and resource (every CONVERTED video inside a folder), with scope that clearly separates it from the single-video sibling panda_duplicate_video. An agent can identify what it does without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operating conditions: only non-external, non-funnel CONVERTED videos are eligible, and dry_run=true is the default preview. It does not name an explicit alternative (e.g., panda_duplicate_video for a single video) or state when to prefer this over bulk paths, so it stops short of full routing guidance.

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