Consent

consent_providers_update

Update an existing consent provider.

Tool

consent_providers_update

Update an existing consent provider.

Update an existing consent provider. cookies: undefined leaves cookies unchanged, [] clears them, [...] replaces the whole set. privacyUrl: null clears the field.

Behavior

HTTP: PATCH /consent/consent/providers/:id

Arguments

Name	Type	Required	Description
id	string	•	Provider id
name	string	—	No description in the catalog.
hosts	array	—	If provided, REPLACES the hosts list. Omit to leave unchanged.
cookies	array	—	If provided, REPLACES the whole cookies set for this provider. Omit to leave unchanged.
category	string	—	Consent category bucket — matches CHECK constraint on consent_providers.category
orderIndex	integer	—	No description in the catalog.
privacyUrl	string	—	null clears the field, undefined leaves it unchanged
description	string	—	Pass empty string to clear; undefined leaves unchanged

Response

Field	Type	Always
id	string	•
name	string	•
hosts	array	•
cookies	array	•
category	string	•
isSystem	boolean	—
createdAt	string	•
updatedAt	string	•
catalogKey	string	—
orderIndex	integer	•
privacyUrl	string	•
description	string	•

Try it

Update an existing consent provider.

When to use

Update an existing consent provider. cookies: undefined leaves cookies unchanged, [] clears them, [...] replaces the whole set. privacyUrl: null clears the field.

Example

Ask your agent something like this:

Update an existing consent provider.

The agent will invoke consent_providers_update with these arguments:

{
  "id": "<id>"
}