Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

List trashed media

list_trashed_media
Read-only

List trashed media files newest first, showing deletion and expiry dates to identify items for restore before permanent deletion.

Instructions

List the media trash, newest first. Each file shows when it was deleted and when it expires; after that it is deleted permanently. A file with isPurging true is being deleted and cannot be restored. Restore with restore_media. Paginated: while hasMore is true, pass nextCursor back as cursor while it is set; if hasMore is true but nextCursor is null, page with the offset instead, and past offset 10000 narrow the filter.

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_trashed_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many files to return, at most 100
cursorNonextCursor from the previous page. The page continues after it in the same filter and sort; leave the skip/offset at 0 when you pass it
offsetNoHow many rows to skip, at most 10000; page past that with cursor

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.146.2
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "nextCursor from the previous page. The page continues after it in the same filter and sort; leave the skip/offset at 0 when you pass it",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / properties / offset / description
      Previous value: -"How many files to skip"New value: +"How many rows to skip, at most 10000; page past that with cursor"
    • changedInput schema / properties / offset / maximum
      Previous value: -9007199254740991New value: +10000
  2. Addedv0.73.2

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only cover read-only safety; the description adds substantial behavior beyond them: default sort order, the deleted/expires timestamps returned per file, permanent deletion after expiry, and the isPurging flag meaning the file cannot be restored. Those are exactly the non-obvious traits an agent needs before acting on results.

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-loaded with purpose and ordering, then lifecycle facts, then restore routing, then paging — a sensible order with no filler. The final paging sentence is a long stacked conditional that takes a careful read, which costs it a point.

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?

No output schema exists, yet the description documents the returned fields (deletion time, expiry, isPurging, hasMore, nextCursor) and the full paging contract, so nothing an agent needs to call this correctly or interpret results is missing. Complexity is low-to-moderate and fully covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, but the description still adds value the schema does not encode: the runtime relationship between hasMore and nextCursor, cursor precedence over offset, and the fallback to offset paging at the 10000 boundary. This is real operational semantics rather than a restatement.

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 scoped resource ("List the media trash") plus a default ordering ("newest first"), which cleanly separates it from list_media without needing the sibling named. An agent can identify the trash-listing operation immediately.

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 explicit downstream routing ("Restore with restore_media") and detailed paging procedure including the hasMore/nextCursor/offset decision tree and the 10000-offset escape hatch. It stops short of an explicit when-not-to-use-this statement (e.g. use list_media for non-trashed files), so it lands just under full marks.

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

Deploy Server

Other Tools