iubenda

Update a service in a site's privacy & cookie policy

update_site_pcp_service

Destructive

Update a PCP service added to a site. Use the primary key returned by list_site_pcp_services or create_site_pcp_service. Send only the fields to change; omitted fields keep their current value.

Input Schema

Name	Required	Description
`id`	Yes	Primary key of the added service (from list/create)
`site_id`	Yes	Site ID
`storage_durations`	No	How long this service's cookies and trackers are stored. Replaces the service's own durations, and switches the service to them unless use_catalog_storage_durations is sent. Only for services that use cookies or trackers. Omit to keep the current value.
`third_party_service`	No	US state privacy laws: true marks the provider as a third party; false marks it as a service provider, processor or contractor. Omit to keep the current value.
`ccpa_constitutes_sale`	No	Processing by this service is a sale of personal information in California (CCPA). Omit to keep the current value.
`selected_processing_places`	No	Array of processing place IDs
`selected_personal_data_types`	No	Array of personal data type IDs
`use_catalog_storage_durations`	No	true shows the catalog's storage durations for this service and clears its own (storage_durations must then be omitted or none); false shows its own. Only for services that use cookies or trackers. Omit to keep the current value.
`other_us_laws_constitutes_sale`	No	Processing by this service is a sale under the other US state privacy laws (Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Nevada and other states). Omit to keep the current value.
`ccpa_sharing_personal_information`	No	Processing by this service is sharing of personal information in California (CCPA). Omit to keep the current value.
`other_us_laws_targeted_advertising`	No	Processing by this service is targeted advertising under the other US state privacy laws (Virginia, Colorado, Connecticut, Utah, Texas, Oregon and other states). Omit to keep the current value.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 15, 2026

addedInput schema / properties / storage_durations

Added value: +{
+  "description": "How long this service's cookies and trackers are stored. Replaces the service's own durations, and switches the service to them unless use_catalog_storage_durations is sent. Only for services that use cookies or trackers. Omit to keep the current value.",
+  "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 / third_party_service

Added value: +{
+  "description": "US state privacy laws: true marks the provider as a third party; false marks it as a service provider, processor or contractor. Omit to keep the current value.",
+  "type": "boolean"
+}

removedInput schema / properties / us_laws_third_party_service

Removed value: -{
-  "description": "US state privacy laws: true marks the provider as a third party; false marks it as a service provider, processor or contractor. Responses report this value as third_party_service. Omit to keep the current value.",
-  "type": "boolean"
-}

addedInput schema / properties / use_catalog_storage_durations

Added value: +{
+  "description": "true shows the catalog's storage durations for this service and clears its own (storage_durations must then be omitted or none); false shows its own. Only for services that use cookies or trackers. Omit to keep the current value.",
+  "type": "boolean"
+}

Changed5 schema fields changedOct 15, 2026

addedInput schema / properties / ccpa_constitutes_sale

Added value: +{
+  "description": "Processing by this service is a sale of personal information in California (CCPA). Omit to keep the current value.",
+  "type": "boolean"
+}

addedInput schema / properties / ccpa_sharing_personal_information

Added value: +{
+  "description": "Processing by this service is sharing of personal information in California (CCPA). Omit to keep the current value.",
+  "type": "boolean"
+}

addedInput schema / properties / other_us_laws_constitutes_sale

Added value: +{
+  "description": "Processing by this service is a sale under the other US state privacy laws (Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Nevada and other states). Omit to keep the current value.",
+  "type": "boolean"
+}

addedInput schema / properties / other_us_laws_targeted_advertising

Added value: +{
+  "description": "Processing by this service is targeted advertising under the other US state privacy laws (Virginia, Colorado, Connecticut, Utah, Texas, Oregon and other states). Omit to keep the current value.",
+  "type": "boolean"
+}

addedInput schema / properties / us_laws_third_party_service

Added value: +{
+  "description": "US state privacy laws: true marks the provider as a third party; false marks it as a service provider, processor or contractor. Responses report this value as third_party_service. Omit to keep the current value.",
+  "type": "boolean"
+}

First observedSep 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The 'send only the fields to change; omitted fields keep their current value' sentence meaningfully discloses PATCH semantics that the annotations do not express. However, annotations declare destructiveHint=true and idempotentHint=false, and the description never explains what is destructive (e.g. that sending storage_durations replaces the service's own durations) — that nuance lives only inside the nested schema, not the description.

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

Conciseness5/5

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

Three short sentences, front-loaded with the operation, then the ID source, then the patch rule. No filler and nothing buried.

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 an 11-parameter, nested, non-idempotent mutation the description covers the essentials an agent needs to call it safely: identity source and partial-update behavior. The remaining gap is that it never distinguishes this tool from update_site_pcp_custom_service, which is the most likely selection error given the sibling set.

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

Parameters3/5

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

Schema description coverage is 100% and the nested properties (storage_durations modes, durations, sale/sharing flags) are documented in detail in the schema, so the schema carries the burden. The description adds only the partial-update rule; it says nothing specific about the 11 parameters, which is the expected baseline when coverage is complete.

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

Purpose4/5

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

States a specific verb and resource: 'Update a PCP service added to a site', which is clearer than the title alone. It does not, however, differentiate itself from the close sibling update_site_pcp_custom_service (catalog service vs. custom service), leaving the agent to infer which update tool applies to which kind of record.

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?

Explicitly names the two sibling tools that produce the required `id` (list_site_pcp_services or create_site_pcp_service), which is real invocation guidance. It also states the partial-update contract. It stops short of saying when to prefer this over update_site_pcp_custom_service or what to do if the record does not exist.

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?