Tokenrip

Delete folder

folder_delete

DestructiveIdempotent

Move a folder, and the files in it, to the trash for 30 days: folder is its id (any kind: personal, team or workspace), or its slug: in workspaceId when given, else in team, else one of your personal folders. They leave listings, and reads of the files answer DELETED through the folder. The files keep their filing and come back with the folder; the slug stays held. Personal: the owner; team: any member; workspace: who may delete its content, with why (expectedWorkspaceRevision optional). Repeating it returns the same dates.

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": {
      "folder": "<folder>"
    },
    "name": "folder_delete"
  }
}

Input Schema

Name	Required	Description
`why`	No	Required for workspace items: one sentence on what the person is trying to accomplish, in their terms, not a description of this edit. Every workspace write takes one; sessions and summaries record themselves from it. At most 300 characters.
`team`	No	With a folder slug: the team (slug or id) it belongs to.
`folder`	Yes	The folder: its id (any kind), or its slug: in workspaceId when given, else in team, else one of your personal folders.
`workspaceId`	No	With a folder slug: the workspace it is in (its id or its slug).
`expectedWorkspaceRevision`	No	Optional, a workspace folder's: refuse (CONFLICT) if the folder changed since this workspace_revision.

Output Schema

Name	Required	Description	Default
`id`	Yes
`type`	Yes
`purgeAt`	Yes
`deletedAt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 24, 2026

changedInput schema / properties / workspaceId / description

Previous value: -"With a folder slug: the workspace it is in."New value: +"With a folder slug: the workspace it is in (its id or its slug)."

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.4/5.0

Behavior5/5

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

Beyond annotations, it explains the soft-delete lifecycle: items leave listings, reads answer DELETED through the folder, files keep their filing and return with the folder, the slug stays held, and repeats return the same dates. Permissions by scope are also disclosed, and nothing contradicts destructiveHint=true or idempotentHint=true.

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?

The purpose is front-loaded and the text is dense but largely free of wasted sentences. However, it is a long run-on sequence of clauses, which makes it harder to scan than a more structured presentation would be.

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 destructive, idempotent soft-delete tool with an output schema and full parameter coverage, the description supplies the essential behavioral and permission context. Return values need not be explained because an output schema exists.

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%, so the schema already documents all five parameters, including slug resolution and the 'why' requirement. The description repeats much of that parameter meaning rather than adding substantial new syntax or edge-case detail, so the baseline of 3 is appropriate.

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?

The description states a specific verb and resource: it moves a folder and its files to the trash for 30 days. It also distinguishes the operation from permanent deletion and from folder updates by explaining the trash lifecycle and what happens to listings and reads.

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?

It gives clear conditions: the folder may be identified by id or slug, resolution depends on workspaceId/team/personal scope, and workspace deletion requires 'why' with optional expectedWorkspaceRevision. It does not explicitly name sibling alternatives such as trash_restore or trash_purge, so it stops short of full when/when-not guidance.

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.