# update_guide_metadata
> Change a Guide's title, description, or topic without creating a content version
Change a [Guide](/key-tasks/guides/)'s title, description, or topic without appending a content version. The guide keeps its UUID and full version history.

## Description

The `update_guide_metadata` tool lets you retitle or re-topic a guide without touching its content. Use it when a guide's title or grouping is outdated — for example after a team reorganization or a product rename.

Provide at least one of `title`, `description`, or `topic`.

To update content, use [`update_guide`](../update-guide) or [`edit_guide_content`](../edit-guide-content) instead.

## Input parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `uuid` | string | Yes | The guide's UUID, as returned by `list_guides` or a previous mutation. |
| `title` | string | No | New human-readable title. Must not be empty when supplied. |
| `description` | string | No | New one-line summary. Pass an empty string (`""`) to clear it. |
| `topic` | string | No | New grouping label — for example `"revenue-billing"` or `"core/metrics"` (no leading or trailing slash). Pass an empty string (`""`) to remove the topic. |

## Output schema

```json
{
  "success": boolean,
  "guide": {
    "id": string,
    "topic": string,           // Updated topic (null when cleared)
    "title": string,           // Updated title
    "description": string,     // Updated description
    "access": string,
    "current_version": number,
    "created_at": string,
    "updated_at": string
  },
  "error": string
}
```

## Example usage

**Move a guide to a different topic:**

```text
Move the order filters guide from order-management to customer-orders
```

```json
{
  "uuid": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "topic": "customer-orders",
  "title": "Customer Order Filters"
}
```

**Update only the description:**

```json
{
  "uuid": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "description": "MRR and ARR definitions, including expansion and churn adjustments"
}
```

**Remove the topic (move the guide to the root level):**

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

## Related

- [`update_guide`](../update-guide) — Append a content version.
- [`edit_guide_content`](../edit-guide-content) — Make targeted in-place content edits.
- [`set_guide_access`](../set-guide-access) — Change a guide's visibility.
- [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%2Fupdate-guide-metadata%2F&page_title=update_guide_metadata&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.