MD_UPDATE_DIVE_METADATA
Updates the title, description, or both of an existing Dive. Metadata updates do not create a new version — current_version is unchanged. To publish new component code, use MD_UPDATE_DIVE_CONTENT.
Syntax
SELECT * FROM MD_UPDATE_DIVE_METADATA(
id := '<dive_id>',
title := '<updated_title>',
description := '<updated_description>'
);
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
id | UUID | Yes | Identifier of the Dive to update. |
title | VARCHAR | No | New Dive title. Omit to leave unchanged. |
description | VARCHAR | No | New Dive description. Omit to leave unchanged. |
Return columns
Returns the updated Dive summary:
| Column | Type | Description |
|---|---|---|
id | UUID | The Dive identifier. |
title | VARCHAR | The current title. |
description | VARCHAR | The current description, or NULL. |
owner_id | UUID | Identifier of the owning user. |
current_version | INTEGER | Latest version number (unchanged by this call). |
created_at | TIMESTAMP WITH TIME ZONE | Original creation timestamp. |
updated_at | TIMESTAMP WITH TIME ZONE | Most recent update timestamp. |
owner_name | VARCHAR | Username of the owner. |
Examples
Rename a Dive:
SELECT id, title, current_version
FROM MD_UPDATE_DIVE_METADATA(
id := '<dive_id>',
title := 'Q1 revenue dashboard'
);
Update only the description:
SELECT id, description
FROM MD_UPDATE_DIVE_METADATA(
id := '<dive_id>',
description := 'Revenue trends filtered to Q1'
);
Related
MD_UPDATE_DIVE_CONTENT— Publish new component code as a new version.MD_GET_DIVE— Inspect the current summary and content.update_diveMCP tool — AI-agent equivalent.