Panda Video

Apply Video Config to Folder

panda_action_apply_video_config_to_folder

Idempotent

Deterministically resolve a folder and apply per-video player config to every CONVERTED video (POST /player?type=video). Supports: default_subtitle (lang code or 'false'), default_audio (dubbing language code or 'false'), on_funnel, and the AI toggles questions/mindmap/abstract. Send only the fields you want to change. 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_apply_video_config_to_folder"
  }
}

Input Schema

Name	Required	Description
`dry_run`	No	true = preview only; false = apply
`mindmap`	No	Enable/disable AI MindMap
`abstract`	No	Enable/disable AI eBook/Abstract
`on_funnel`	No	Enable/disable funnel integration
`questions`	No	Enable/disable AI Quiz
`folder_ref`	Yes	Folder name, ID, or dashboard URL
`default_audio`	No	Default audio language — code of a dubbing the videos have (e.g. 'es') or 'false' for the original audio. Only takes effect with the dubbing item on in the gear menu and without lipsync.
`idempotency_key`	No	Reserved client-supplied retry key
`default_subtitle`	No	Default subtitle language code (e.g. 'pt-BR') or 'false' to disable

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026

addedInput schema / properties / default_audio

Added value: +{
+  "description": "Default audio language — code of a dubbing the videos have (e.g. 'es') or 'false' for the original audio. Only takes effect with the dubbing item on in the gear menu and without lipsync.",
+  "type": "string"
+}

removedInput schema / properties / panda_branding

Removed value: -{
-  "description": "Show/hide Panda logo branding",
-  "type": "boolean"
-}

First observedOct 5, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false, idempotent=true), the description discloses that only CONVERTED videos are touched and that the default is a non-mutating preview via dry_run, which meaningfully de-risks invocation. It does not say what happens to skipped/non-converted videos or whether applied changes take effect immediately, leaving a small gap.

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?

Three dense sentences, front-loaded with verb, scope and endpoint, then the field list, then the dry-run safety note. The middle enumeration overlaps the schema somewhat but earns its place as a scannable summary; no filler is present.

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 9-parameter mutation tool with no output schema, the description covers scope, partial-update semantics and preview behavior adequately. Missing are permission requirements, the shape of the dry-run preview response, and whether changes are reversible or immediately live.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds value by naming the changeable fields together with their accepted value forms (language code or the literal 'false' sentinel for default_subtitle/default_audio) and by reiterating the dry_run default. It also signals partial-update semantics for the optional toggles.

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+resource ('apply per-video player config') and a precise scope ('every CONVERTED video'), plus the underlying endpoint. It does not explicitly name which sibling to prefer (e.g. set_default_subtitle_for_folder or set_folder_player_control), so it falls short of the top mark but an agent can still tell what this tool does.

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?

'Send only the fields you want to change' and 'dry_run=true (default) previews' give real procedural guidance on partial updates and safe previewing. However there is no statement of when to choose this over the many similar folder-level config siblings, so usage is implied rather than fully routed.

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

All Panda Video tools Inspect

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.