Skip to main content
Glama

delete_video

Destructive

Moves a video and its settings to the out/trash folder instead of permanent deletion. Ask the user first, then call with user_confirmed=true.

Instructions

Moves a video and its settings to the out/trash folder (not deleted for good). Ask the user first, then call with user_confirmed=true.

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": "<video>"
    },
    "name": "delete_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoYes
user_confirmedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the bar is lower, yet the description adds substantive context: the effect is recoverable (moved to trash, settings preserved) and requires a user-confirmation gate. It does not say whether/how items are restored from trash or how long they persist, which keeps it from a 5.

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?

Two short sentences with zero filler; the operation and its non-permanent nature are front-loaded, and the confirmation instruction follows as the actionable next step.

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 two-parameter mutation with no output schema and annotations that already flag destructiveness, the description covers the essential facts: effect, reversibility, and the confirmation protocol. The only real gap is the format/semantics of the video identifier.

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 0%, so the description must carry parameter meaning. It does explain user_confirmed=true as the post-confirmation flag (valuable given the default of false), but says nothing about what the required "video" value should be — an ID, name, or path — leaving half the parameters undocumented.

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?

"Moves a video and its settings to the out/trash folder" gives a specific verb (move, not delete) and resource (video plus its settings), and the parenthetical "(not deleted for good)" immediately distinguishes this soft-delete from any truly destructive sibling operation.

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?

The description prescribes an explicit workflow: ask the user first, then invoke with user_confirmed=true. That is real when/how guidance rather than implied usage. It stops short of a 5 because no alternatives or when-not conditions are named, though no sibling delete variant appears to exist.

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