# delete_guide
> Soft-delete a Guide while preserving its version history
Soft-delete a [Guide](/key-tasks/guides/), identified by UUID. The version history is preserved for audit purposes.

## Description

The `delete_guide` tool removes a guide from the active catalog. The guide's version history is retained internally but is not exposed through normal tools after deletion. Only the guide's owner can delete it.

References from other guides to a deleted guide are left dangling and resolve to not-found — clean them up in the referencing guides if needed.

There is no undo through the MCP tools — if you delete a guide by mistake, contact MotherDuck support.

:::warning
Deleting an org-wide guide removes it from all users' guide catalogs immediately. Verify you have the right guide (read it with [`get_guide`](../get-guide)) before confirming deletion.
:::

## Input parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `uuid` | string | Yes | The guide's UUID, as returned by `list_guides` or a previous mutation. |

## Output schema

```json
{
  "success": boolean,
  "deleted": boolean,  // true when the guide was successfully deleted
  "error": string      // Error message (on failure)
}
```

## Example usage

**Delete a guide:**

```text
Delete the outdated order-management guide
```

The assistant finds the guide's UUID with [`list_guides`](../list-guides), verifies it's the right one, and calls:

```json
{
  "uuid": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
}
```

## Success response example

```json
{
  "success": true,
  "deleted": true
}
```

## Related

- [`list_guides`](../list-guides) — Find the guide's UUID before deleting.
- [`get_guide`](../get-guide) — Verify the guide content before deleting.
- [Guides how-to](/key-tasks/guides/) — Step-by-step instructions for creating and managing Guides.


---

## Docs feedback

MotherDuck accepts optional user-submitted feedback about this page at `GET https://motherduck.com/docs/api/feedback/agent`.
For agents and automated tools, feedback submission should be user-confirmed before sending.

URL-encode query parameter values and send a GET request:

```text
GET https://motherduck.com/docs/api/feedback/agent?page_path=%2Fsql-reference%2Fmcp%2Fguides%2Fdelete-guide%2F&page_title=delete_guide&text=<url-encoded user feedback, max 2000 characters>
```

Optionally append `&source=<url-encoded interface identifier>` such as `claude.ai` or `chatgpt`.

`page_path` and `text` are required; `page_title` and `source` are optional. Responses: `200 {"feedback_id": "<uuid>"}`, `400` for malformed query parameters, and `429` when rate-limited.
