Previews

delete_preview

Permanently delete a preview project, including all versions and assets, by its slug. Use it to remove obsolete previews and their associated resources.

Instructions

Permanently delete a preview project and all its versions and assets.

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": {
      "slug": "<slug>"
    },
    "name": "delete_preview"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	The preview slug to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 6, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the two most important traits: the operation is irreversible ('Permanently') and it cascades to all versions and assets. It says nothing about required permissions, whether the slug must exist, or what happens on a missing slug, which leaves meaningful gaps for a destructive write.

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?

One sentence, front-loaded with the irreversible nature and action, with zero filler. Every clause ('Permanently', 'all its versions and assets') carries distinct 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?

For a single-parameter, no-output-schema deletion tool, the description covers the action, irreversibility, and cascade scope, which is essentially everything needed to call it correctly. Only error/confirmation behavior is left unstated, a minor gap at this complexity level.

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?

There is a single parameter with 100% schema description coverage ('The preview slug to delete'), and the description reinforces that the slug identifies the object being destroyed, which is adequate for a one-param tool. No format or sourcing detail for the slug is added beyond the schema.

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?

The description gives a specific verb and resource ('Permanently delete a preview project') and adds the scope of what is removed ('all its versions and assets'). It is unambiguous versus siblings like list_previews, create_preview, and update_preview, though it does not name them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the word 'Permanently' and by the tool name itself; there is no explicit statement of when to choose deletion versus update_preview, and no prerequisite or confirmation guidance. An agent can infer the use case but gets no routing rules.

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

Deploy Server