Tokenrip

Delete bundle

bundle_delete

DestructiveIdempotent

Move a bundle to the trash for 30 days: its live site stops serving and its slug stays held. The owner or a platform admin; 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": {
      "bundleId": "<bundleId>"
    },
    "name": "bundle_delete"
  }
}

Input Schema

Name	Required	Description	Default
`why`	No	Optional, accepted and not recorded: this write keeps no workspace history. If you send one, one sentence on what the person is trying to accomplish. At most 300 characters.
`bundleId`	Yes	The bundle: its id, your slug for it, its live URL or its page URL.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

While annotations already flag destructiveHint and idempotentHint, the description adds non-obvious consequences the annotations cannot convey: the live site stops serving, the slug remains held, retention is 30 days, and repeated calls return the same dates. That is exactly the extra context an agent needs before triggering a destructive action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences, front-loaded with the action and its consequences, then authorization and idempotency. Nothing is wasted and nothing important is buried.

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?

The output schema covers return values (the dates), and the description covers the destructive consequences, retention period, authorization, and idempotency. An agent has everything needed to decide and call correctly.

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 both parameters (bundleId accepted in id/slug/URL forms, and the unrecorded 'why') are fully documented in the schema. The description adds no parameter-level detail beyond the owner/admin authorization note, so the baseline 3 applies.

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 with its exact semantics: 'Move a bundle to the trash for 30 days.' The soft-delete framing plus 'slug stays held' distinguishes it from a hard delete and implicitly from trash_purge/trash_restore without needing to name them.

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 a clear precondition ('The owner or a platform admin') and the 30-day window that tells an agent this is recoverable, which is the key usage consideration. It stops short of explicitly naming the alternative tools (trash_restore for undo, trash_purge for permanent removal).

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.