Skip to main content
Glama
Sign In

Panda Video

by com.pandavideo
OverviewDiscussionsAdmin

Delete Profile

panda_delete_profile
DestructiveIdempotent

Delete a player profile. The default profile ('Padrão') cannot be deleted. A profile with no videos is deleted directly. A profile WITH videos needs strategy — ask the user which one: 'keep' = each video keeps its current look (gets its own copy of the profile's settings); 'migrate' = the videos move to target_profile_id. Up to 5 videos are processed immediately; more are queued (status 'pending') and the profile disappears once all videos are moved. If any video fails, the profile is NOT deleted.

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": {
      "profile_id": "<profile_id>"
    },
    "name": "panda_delete_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
strategyNoRequired when the profile has videos: 'keep' (videos keep their look) or 'migrate' (videos move to target_profile_id)
profile_idYesProfile ID
target_profile_idNoProfile that receives the videos — required with strategy 'migrate'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / strategy
      Added value: +{
+  "description": "Required when the profile has videos: 'keep' (videos keep their look) or 'migrate' (videos move to target_profile_id)",
+  "enum": [
+    "keep",
+    "migrate"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / target_profile_id
      Added value: +{
+  "description": "Profile that receives the videos — required with strategy 'migrate'",
+  "type": "string"
+}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare destructive/idempotent/openWorld; the description adds far more: 5-video synchronous batch, queueing with 'pending' status, profile disappearance after all videos move, and the critical atomicity guarantee that the profile is NOT deleted if any video fails. That failure-mode disclosure is exactly what an agent needs before invoking a destructive tool.

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?

Front-loads the action, then the guard condition, then the branch logic, then the async/failure behavior — a natural decision order for the agent. Dense but zero filler sentences.

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

Completeness5/5

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

For a destructive, partially-asynchronous mutation with no output schema, it covers preconditions, branching, batching limits, queue status, and failure semantics. Nothing essential to a correct call is missing.

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 baseline is 3; the description earns a bump by explaining the consequence of each strategy ('keep' = videos get their own copy of settings vs 'migrate' = videos move to target_profile_id) and when strategy is required. It largely mirrors the schema text but adds the outcome semantics.

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?

Specific verb+resource ('Delete a player profile') with immediate differentiation from siblings like panda_restore_profile and panda_update_profile by stating the deletion semantics. An agent can tell exactly what this 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 Guidelines5/5

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

Explicitly states the guard condition (default 'Padrão' profile cannot be deleted), when a strategy is mandatory (profile with videos), and even instructs the agent to ask the user which strategy to use. This is unusually actionable 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