Wistia MCP Server

Update Folder Sharing

update_folder_sharing

Destructive

Update sharing permissions for a Wistia folder, including admin, share, upload, and download access for users or groups. Confirm before applying changes to avoid unintended access or notifications.

Instructions

Updates a sharing on a folder.

Requires api token with one of the following permissions

Read, update & delete anything

Tokens with the "Act with a team member's permissions" permission (all:delegate_to_contact_permissions scope) can also be used. Requests made with such a token are authorized using the permissions of the contact assigned to the token. Requires confirm=true for the requested mutation. May share access, notify people or incur provider charges.

Input Schema

Name	Required	Description
`account`	No	Named private Wistia account; selects credentials, not a remote account ID.
`confirm`	No	Set true only when the user asked for exactly this action.
`payload`	No	Complete JSON request body instead of body flags. Supports current nested customization, caption and nullable values.
`sharing`	No
`folder_id`	Yes	ID of the folder
`sharing_id`	Yes	ID of the sharing to be updated
`payload_file`	No	Regular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv3.0.0Oct 7, 2026

addedInput schema / $defs

Added value: +{
+  "sharing": {
+    "properties": {
+      "canDownload": {
+        "description": "Allow the user or group to download media from the folder.",
+        "type": "boolean"
+      },
+      "canShare": {
+        "description": "Allow the user or group to share the folder with others.",
+        "type": "boolean"
+      },
+      "canUpload": {
+        "description": "Allow the user or group to upload media to the folder.",
+        "type": "boolean"
+      },
+      "isAdmin": {
+        "description": "Give this user admin rights to the folder.",
+        "type": "boolean"
+      }
+    },
+    "type": "object",
+    "unevaluatedProperties": false
+  }
+}

changedInput schema / properties / confirm / description

Previous value: -"Must be true for the specific user-requested write."New value: +"Set true only when the user asked for exactly this action."

addedInput schema / properties / payload / properties / sharing / $ref
```
Added value: +"#/$defs/sharing"
```

removedInput schema / properties / payload / properties / sharing / properties

Removed value: -{
-  "canDownload": {
-    "description": "Allow the user or group to download media from the folder.",
-    "type": "boolean"
-  },
-  "canShare": {
-    "description": "Allow the user or group to share the folder with others.",
-    "type": "boolean"
-  },
-  "canUpload": {
-    "description": "Allow the user or group to upload media to the folder.",
-    "type": "boolean"
-  },
-  "isAdmin": {
-    "description": "Give this user admin rights to the folder.",
-    "type": "boolean"
-  }
-}

removedInput schema / properties / payload / properties / sharing / type
```
Removed value: -"object"
```
removedInput schema / properties / payload / properties / sharing / unevaluatedProperties
```
Removed value: -false
```
addedInput schema / properties / sharing / $ref
```
Added value: +"#/$defs/sharing"
```

removedInput schema / properties / sharing / properties

Removed value: -{
-  "canDownload": {
-    "description": "Allow the user or group to download media from the folder.",
-    "type": "boolean"
-  },
-  "canShare": {
-    "description": "Allow the user or group to share the folder with others.",
-    "type": "boolean"
-  },
-  "canUpload": {
-    "description": "Allow the user or group to upload media to the folder.",
-    "type": "boolean"
-  },
-  "isAdmin": {
-    "description": "Give this user admin rights to the folder.",
-    "type": "boolean"
-  }
-}

removedInput schema / properties / sharing / type
```
Removed value: -"object"
```
removedInput schema / properties / sharing / unevaluatedProperties
```
Removed value: -false
```

First observedv2.0.0Oct 2, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare destructive/non-idempotent/open-world, and the description goes beyond them by disclosing auth scope requirements, the delegation authorization model, the confirm=true gate, and real side effects (sharing access, notifying people, provider charges). It does not explain partial-vs-full update semantics for unspecified sharing fields, which is the main remaining behavioral gap.

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?

Content is front-loaded (purpose first, then requirements and side effects) and every sentence carries information. The inline markdown heading and fenced code block for the permission name add some visual noise for what is a short list.

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 mutation tool with a nested schema, no output schema, and strong annotations, the description covers auth, confirmation, and side effects adequately. It stops short of clarifying return behavior or whether the update is a merge or replacement, but the agent has enough to invoke it correctly.

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 86%, so the schema already documents all seven parameters including the nested sharing flags, payload, payload_file, and confirm. The description adds no parameter-level detail beyond echoing the confirm=true requirement, so the baseline 3 applies.

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: "Updates a sharing on a folder." An agent can tell it modifies an existing sharing rather than creating or deleting one, but it never names the closely related siblings (create_folder_sharing, delete_folder_sharing, get_folder_sharing) to sharpen the boundary.

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

Usage Guidelines3/5

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

Provides authentication prerequisites (required permission scope, delegation scope) and the confirm=true condition, which is useful context for whether the call can succeed. However, it gives no when-to-use vs alternatives guidance — nothing distinguishing this from create/delete_folder_sharing or update_sharing_customizations.

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

Deploy Server