iubenda

Update privacy & cookie policy

update_privacy_cookie_policy

Destructive

Update the Privacy & Cookie Policy document for a site: its badge style and its cookie policy (add or remove it, strictly necessary cookies, storage durations of the site's own cookies). Send only the fields to change; omitted fields keep their current value. A request with several fields is all-or-nothing. strictly_necessary_cookies and storage_durations need a version 2 cookie policy: a site with a legacy cookie policy is refused with "requires the privacy policy to have a cookie policy" even though has_cookie_policy is true. Do not retry the same call; tell the user instead.

Input Schema

Name	Required	Description
`site_id`	Yes	Site ID
`configuration`	No	Policy display configuration
`has_cookie_policy`	No	true adds the cookie policy to the privacy policy, false removes it, in every language. Adding it can be refused if the site's plan does not include it. Omit to keep the current value.
`storage_durations`	No	How long the site's own cookies and trackers are stored. Replaces the current durations. Requires a cookie policy with strictly_necessary_cookies true; both can be set in the same call. Omit to keep the current durations.
`strictly_necessary_cookies`	No	Whether the site uses technical cookies that are strictly necessary for the operation or delivery of the service. Requires a cookie policy, which can be added in the same call with has_cookie_policy. Omit to keep the current value.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 15, 2026

changedInput schema / properties / configuration / properties / badge_style / description

Previous value: -"Badge visual style"New value: +"Badge visual style. Required unless the call sets has_cookie_policy, strictly_necessary_cookies or storage_durations."

addedInput schema / properties / has_cookie_policy

Added value: +{
+  "description": "true adds the cookie policy to the privacy policy, false removes it, in every language. Adding it can be refused if the site's plan does not include it. Omit to keep the current value.",
+  "type": "boolean"
+}

addedInput schema / properties / storage_durations

Added value: +{
+  "description": "How long the site's own cookies and trackers are stored. Replaces the current durations. Requires a cookie policy with strictly_necessary_cookies true; both can be set in the same call. Omit to keep the current durations.",
+  "properties": {
+    "cookies": {
+      "items": {
+        "properties": {
+          "duration": {
+            "anyOf": [
+              {
+                "enum": [
+                  "session",
+                  "indefinite"
+                ],
+                "type": "string"
+              },
+              {
+                "properties": {
+                  "amount": {
+                    "maximum": 2147483647,
+                    "minimum": 1,
+                    "type": "integer"
+                  },
+                  "unit": {
+                    "enum": [
+                      "second",
+                      "minute",
+                      "hour",
+                      "day",
+                      "month",
+                      "year"
+                    ],
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "amount",
+                  "unit"
+                ],
+                "type": "object"
+              }
+            ],
+            "description": "\"session\", \"indefinite\", or an object with a whole-number amount and a unit"
+          },
+          "name": {
+            "description": "Cookie or tracker name, 1 to 50 characters, counting & < > as their HTML escapes",
+            "maxLength": 50,
+            "minLength": 1,
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "duration"
+        ],
+        "type": "object"
+      },
+      "maxItems": 100,
+      "minItems": 1,
+      "type": "array"
+    },
+    "maximum_duration": {
+      "anyOf": [
+        {
+          "enum": [
+            "session",
+            "indefinite"
+          ],
+          "type": "string"
+        },
+        {
+          "properties": {
+            "amount": {
+              "maximum": 2147483647,
+              "minimum": 1,
+              "type": "integer"
+            },
+            "unit": {
+              "enum": [
+                "second",
+                "minute",
+                "hour",
+                "day",
+                "month",
+                "year"
+              ],
+              "type": "string"
+            }
+          },
+          "required": [
+            "amount",
+            "unit"
+          ],
+          "type": "object"
+        }
+      ],
+      "description": "\"session\", \"indefinite\", or an object with a whole-number amount and a unit"
+    },
+    "mode": {
+      "description": "none: not specified. maximum: one maximum duration across all cookies and trackers, given in maximum_duration (required for this mode). per_cookie: one duration for each cookie or tracker, given in cookies (required for this mode).",
+      "enum": [
+        "none",
+        "maximum",
+        "per_cookie"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "mode"
+  ],
+  "type": "object"
+}

addedInput schema / properties / strictly_necessary_cookies

Added value: +{
+  "description": "Whether the site uses technical cookies that are strictly necessary for the operation or delivery of the service. Requires a cookie policy, which can be added in the same call with has_cookie_policy. Omit to keep the current value.",
+  "type": "boolean"
+}

First observedSep 7, 2026

TDQS

A4.5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well past the annotations: it discloses atomicity ("A request with several fields is all-or-nothing"), the exact refusal condition for legacy v1 cookie policies and the exact error text, and forbids retrying. These are non-obvious behavioral traits an agent cannot derive from destructiveHint/idempotentHint alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose, then partial-update rule, then atomicity, then the failure mode — a sensible ordering with no filler. The parenthetical field list in the first sentence is slightly compressed and reads awkwardly, but every sentence still carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, non-idempotent mutation with five params, no output schema and full schema coverage, the description covers merge semantics, cross-field dependencies and error recovery — the gaps an agent would otherwise trip on. It stops short of stating what the call returns or what permission level is needed, but nothing essential to calling it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics beyond it: which fields require a v2 cookie policy, that has_cookie_policy can be combined with strictly_necessary_cookies in one call, and the omit-to-preserve rule. It does not restate the badge_style enum or the duration object shape, which the schema already handles.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Update the Privacy & Cookie Policy document for a site") and immediately enumerates the two editable surfaces: badge style and cookie policy. This distinguishes it from the neighboring update_site, update_terms_conditions and update_cookie_solution tools without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the invocation model clearly ("Send only the fields to change; omitted fields keep their current value") and gives an explicit failure-handling directive ("Do not retry the same call; tell the user instead"). It does not name sibling alternatives such as create_privacy_cookie_policy or get_privacy_cookie_policy, so the exclusions are implicit rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All iubenda tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?