Wistia MCP Server

Update share link

update_share_link

Destructive

Update or create a share link for a single media and set its visibility to control who can view it. Use to change access permissions or generate a new media link.

Instructions

Updates the share link for a single media. If the media does not have a share link yet, one is created with the supplied visibility.

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.
`media_id`	Yes	The hashed ID of the media.
`visibility`	No
`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: +{
+  "visibility": {
+    "description": "Controls who can view the media via this share link.\n\n- `unlocked`: anyone with the link can view the media.\n- `account`: only signed-in members of the media's account can view.\n- `locked`: only contacts with access to the media's folder can view.\n- `domain_verified`: only viewers signed in with an email address at a\n  domain verified on the media's account can view. Requires the account\n  to be enrolled in the domain validation gate; otherwise setting this\n  value returns 400.\n",
+    "enum": [
+      "unlocked",
+      "account",
+      "locked",
+      "domain_verified"
+    ],
+    "type": "string"
+  }
+}

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 / visibility / $ref
```
Added value: +"#/$defs/visibility"
```

removedInput schema / properties / payload / properties / visibility / description

Removed value: -"Controls who can view the media via this share link.\n\n- `unlocked`: anyone with the link can view the media.\n- `account`: only signed-in members of the media's account can view.\n- `locked`: only contacts with access to the media's folder can view.\n- `domain_verified`: only viewers signed in with an email address at a\n  domain verified on the media's account can view. Requires the account\n  to be enrolled in the domain validation gate; otherwise setting this\n  value returns 400.\n"

removedInput schema / properties / payload / properties / visibility / enum

Removed value: -[
-  "unlocked",
-  "account",
-  "locked",
-  "domain_verified"
-]

removedInput schema / properties / payload / properties / visibility / type
```
Removed value: -"string"
```
addedInput schema / properties / visibility / $ref
```
Added value: +"#/$defs/visibility"
```

removedInput schema / properties / visibility / description

Removed value: -"Controls who can view the media via this share link.\n\n- `unlocked`: anyone with the link can view the media.\n- `account`: only signed-in members of the media's account can view.\n- `locked`: only contacts with access to the media's folder can view.\n- `domain_verified`: only viewers signed in with an email address at a\n  domain verified on the media's account can view. Requires the account\n  to be enrolled in the domain validation gate; otherwise setting this\n  value returns 400.\n"

removedInput schema / properties / visibility / enum

Removed value: -[
-  "unlocked",
-  "account",
-  "locked",
-  "domain_verified"
-]

removedInput schema / properties / visibility / type
```
Removed value: -"string"
```

First observedv2.0.0Oct 2, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond annotations by disclosing the create-if-missing upsert behavior, the exact authorization scopes needed, the confirm=true gate, and the side-effect warning (may share access, notify people, or incur provider charges). These are non-obvious traits an agent must know before invoking a destructive mutation.

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 the core action and the upsert caveat in the first two sentences, then segments permissions in a header block. Slightly verbose in the token-permission boilerplate but every section carries actionable information.

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

Completeness5/5

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

No output schema exists, and the description compensates with auth requirements, confirmation gating, side-effect disclosures, and the create-vs-update branch. Nothing an agent needs to call this correctly is missing.

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 coverage is 83%, so the schema already documents media_id, visibility, confirm, payload, and payload_file in detail. The description only alludes to 'supplied visibility' and reinforces the confirm requirement, adding little syntax or format detail beyond the schema.

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 ('Updates the share link for a single media') and immediately clarifies the upsert semantics (creates one if absent). An agent can distinguish it from get_share_link, resolve_share_link, and delete_share_link purely from the description.

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?

Gives clear operational prerequisites: required token permissions, the delegate-to-contact scope variant, and the confirm=true requirement for the mutation. It does not explicitly name or exclude sibling tools, but the verb+resource makes the boundary obvious.

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

Deploy Server