updateRedirect
Idempotent
Update an existing redirect record by its ID to modify destination or source path. Writes changes live; fields omitted remain unchanged.
Instructions
Update a redirect - Update an existing redirect record by ID. Fields omitted are untouched. Writes live data.
Use when: adjusting an existing rule's destination or source path. Rare - most redirects are create-once.
Required: redirect_id.
type is wrapper-managed: not exposed as an input. All redirects created via this MCP are custom; other BD type values are reserved for system-generated redirects.
See also: createRedirect (add new), deleteRedirect (remove permanently).
Returns: { status: "success", message: {...updatedRecord} } - the full updated record after changes applied.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| redirect_id | Yes | Redirect primary key (required to identify record) | |
| old_filename | No | The old URL path being redirected from, relative to the domain root (e.g. old-slug, not the full URL) | |
| new_filename | No | The new destination URL path | |
| db_id | No | Database record ID of the source content object this redirect was generated from (0 if not tied to a record) | |
| id | No | Legacy secondary identifier; typically 0 for system-generated redirects | |
| _clear_fields | No | Column names to clear to empty string. Available on every `update*` operation. Works on base columns AND EAV/`users_meta` rows (rows preserved with `value=""`). To actually clear a field you MUST use this parameter — sending the field with `""` alone is a no-op (BD drops empty values). To remove a `users_meta` row entirely, use `deleteUserMeta`. See **Rule: Clearing fields**. Example: `_clear_fields: ["h2", "hero_link_url"]`. |