Skip to main content
Glama

List deleted videos

list_trash
Read-only

Lists videos in the Recordful trash with video ID, title, deletion date, and permanent removal time 7 days later; read-only and available on Recordful Pro after checking the account plan.

Instructions

Recordful Pro only (check get_status recorder.account.plan first). Videos in trash that the user can see: videoId, title, when it was deleted and when it's gone for good (7 days later). Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_trash"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely new context: the plan gate, per-user visibility scoping, and the 7-day retention window before permanent deletion. The closing 'Read-only' partly restates the annotation rather than adding to it.

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?

Front-loads the eligibility constraint, then the returned data, then the safety note — a sensible order with almost no filler. The phrasing is telegraphic ('Recordful Pro only', parentheses) but each fragment carries information.

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?

With no parameters and no output schema, the description correctly supplies the return fields and the retention semantics an agent needs to interpret results. Pagination behavior and result-size limits are unstated, a minor gap for a listing tool that could return many trashed videos.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline applies. The description instead spends its words on return content and prerequisites, which is the right allocation for a no-arg tool.

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 and resource — deleted videos visible to the user — and enumerates the returned fields (videoId, title, deletion time, permanent-deletion time). An agent can distinguish it from list_videos, but the description never explicitly contrasts with list_videos or restore_video, leaving the sibling boundary to be inferred from names.

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?

Gives an explicit precondition — Recordful Pro plans only — and routes the agent to get_status recorder.account.plan to verify it, which is concrete when-to-use guidance. It stops short of stating an exclusion case (e.g. what to call instead when the plan check fails).

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