Skip to main content
Glama
Sign In

Panda Video

by com.pandavideo
OverviewDiscussionsAdmin

Set Video Offline

panda_set_video_offline
DestructiveIdempotent

Configure offline playback for a video (mobile app feature)

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": {
      "video_id": "<video_id>",
      "enabled": "<enabled>"
    },
    "name": "panda_set_video_offline"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYesEnable or disable offline playback
video_idYesVideo ID
expire_daysNoDays until offline access expires (null = never)
external_link_urlNoExternal link URL
external_link_textNoExternal link button text
external_link_enabledNoShow external link button

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, and openWorldHint=true. The description adds only that this is a mobile-app feature, with no explanation of what becomes unavailable when offline playback is disabled, what expire_days or external-link changes do, or any auth or side-effect details for a destructive mutation.

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?

The description is a single front-loaded sentence with no wasted words. It is efficiently structured, though the parenthetical scope note is minor and the brevity contributes to the lack of behavioral detail elsewhere.

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?

For a destructive mutation with six parameters and no output schema, the description is too sparse. It does not explain the effect of toggling offline playback, expiration behavior, or the external-link fields, leaving critical operational context to inference despite rich annotations.

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 six parameters are already documented in the schema. The description adds no parameter-specific meaning beyond that structured documentation, making the baseline 3 appropriate.

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 states a specific verb ('Configure') and resource ('offline playback for a video'), and adds a mobile-app scope. However, it does not distinguish this video-level tool from the sibling folder-level tool panda_action_set_folder_videos_offline.

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

Usage Guidelines2/5

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

No explicit when-to-use guidance or alternative selection criteria are provided. The parenthetical '(mobile app feature)' gives context but does not tell the agent when this tool should be chosen over related offline or folder-level operations.

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