Tokenrip

List trash

trash_list

Read-onlyIdempotent

List what is in the trash, newest first, with when each item was deleted, by whom, and when it purges (30 days after deletion). Omit workspaceId, team and account for your own trash (standalone artifacts, bundles, personal folders, personal workspaces); pass team for a team's folders and workspaces, or workspaceId for the artifacts and folders deleted in that workspace. account (an account id or alias) reads another account's own trash, for a platform admin only (anyone else: FORBIDDEN); a platform admin also reads any team's and any workspace's trash. type lists one type only (one that trash holds). A deleted folder or workspace is one entry. Restore an entry with trash_restore, by its id.

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": "trash_list"
  }
}

Input Schema

Name	Required	Description
`team`	No	A team's trash, by slug or id: its folders and workspaces.
`type`	No	Only entries of this type. Your own trash holds all four; a team's folders and workspaces; a workspace's artifacts and folders.
`limit`	No	Page size, 1 to 100.
`offset`	No	The nextOffset of the previous page.
`account`	No	Another account's own trash, by account id or alias (platform admins only; anyone else is refused FORBIDDEN).
`workspaceId`	No	A workspace's trash, by its id or its slug: the artifacts and folders deleted in it.

Output Schema

Name	Required	Description	Default
`items`	Yes
`nextOffset`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 12, 2026

changedInput schema / properties / workspaceId / description

Previous value: -"A workspace's trash, by its id or its slug: the artifacts and folders deleted in it (an external member sees shared items only)."New value: +"A workspace's trash, by its id or its slug: the artifacts and folders deleted in it."

Changed5 schema fields changedOct 24, 2026

changedInput schema / properties / workspaceId / description

Previous value: -"A workspace's trash: the artifacts and folders deleted in it (an external member sees shared items only)."New value: +"A workspace's trash, by its id or its slug: the artifacts and folders deleted in it (an external member sees shared items only)."

removedInput schema / properties / workspaceId / format
```
Removed value: -"uuid"
```
addedInput schema / properties / workspaceId / maxLength
```
Added value: +64
```
addedInput schema / properties / workspaceId / minLength
```
Added value: +1
```

removedInput schema / properties / workspaceId / pattern

Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower, yet the description adds real behavior: newest-first ordering, the fields returned per entry, the 30-day purge window, the FORBIDDEN outcome for non-admins using account, and the fact that a deleted folder or workspace counts as a single entry. That is substantive context an agent cannot get from the annotations.

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 the core action and output shape, then scope selection, then admin constraints. Dense semicolon-chained sentences pack a lot of routing logic, which borders on hard-to-scan but carries no filler.

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 six-parameter, zero-required listing tool with an output schema, the description covers scope selection, ordering, permissions, and purge timing — everything needed to call it correctly. Return-value details are correctly left to the output schema.

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, but the description adds cross-parameter semantics the schema does not: which scope fields to omit vs. pass, that the admin-only restriction applies to account, and that type restricts to one type the trash actually holds. This meaningfully improves correct parameter selection.

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?

Opens with a specific verb and resource ("List what is in the trash") and immediately adds scope-defining traits: ordering (newest first), returned metadata (deleted-at, deleted-by, purge-at), and the 30-day purge rule. It is clearly distinct from sibling list tools such as artifact_list or folder_list, which enumerate live resources.

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 parameter-based routing: omit scope fields for your own trash, pass team for a team's folders/workspaces, workspaceId for that workspace's items, account for another account's trash (admin only). It also names trash_restore as the follow-up action for entries found here. The only gap is that it does not explicitly contrast against live-resource listers (artifact_list, folder_list) for agents unsure whether an item is deleted.

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

All Tokenrip tools Inspect

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.