Skip to main content
Glama

Restore a deleted video

restore_video
Idempotent

Restore a trashed video to your workspace with its original links intact. Use it to recover recordings deleted from the trash, if you recorded the video or own the workspace.

Instructions

Recordful Pro only (check get_status recorder.account.plan first). Bring a video back out of trash (list_trash shows them), with its links as before. Only the person who recorded it, or the workspace owner, can.

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": {
      "videoId": "<videoId>"
    },
    "name": "restore_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoIdYesThe video in trash to bring back (from list_trash).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, idempotent behavior; the description adds real context beyond them — the plan gate, the permission constraint, and the guarantee that links are restored as before. It does not say what happens if the video is not in trash or was permanently purged, which is the main remaining 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 short sentences, no filler, and the irreversible prerequisites are front-loaded. The final sentence is elliptical ('or the workspace owner, can.'), which reads awkwardly and slightly obscures the action being permitted.

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 one-parameter mutation with no output schema, the description covers plan gating, permissions, identifier source, and the post-restore state of links. Only failure modes (video absent from trash, unauthorized caller) are left unspecified.

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% and the videoId property already documents the UUID pattern and points to list_trash, so the description adds little beyond repeating that provenance. Baseline 3 applies when the schema carries the parameter burden.

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 and resource — 'Bring a video back out of trash' — and immediately scopes it to videos found via list_trash, so an agent can distinguish it from delete_video and list_trash without opening any 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?

Gives explicit preconditions (Recordful Pro plan, verified via get_status recorder.account.plan), names the sibling that supplies the required identifier (list_trash), and states the authorization rule (recorder or workspace owner). When-to-use, prerequisites, and eligibility are all covered.

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