Wistia MCP Server

Update Channel Episode

update_channel_episode

Destructive

Update an existing Wistia channel episode's title, summary, publish status, schedule, media association, podcast settings, and episode notes.

Instructions

Updates an existing channel episode in a channel.

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
`title`	No	The episode's title. If not provided, the channel episode uses the title of the media used to create it.
`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.
`summary`	No	A short summary of the episode that is displayed when space is limited.
`publish_at`	No	The date and time when the episode is scheduled to be published in UTC timezone.
`description`	No	The episode's description or episode notes.
`payload_file`	No	Regular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
`episode_notes`	No	Additional notes for the episode.
`publish_status`	No	The status of whether or not the episode has been published to your channel.
`media_hashed_id`	No	The unique alphanumeric identifier for the media associated with this channel episode.
`podcast_settings`	No
`channel_episode_hashed_id`	Yes	The hashed id of the Channel Episode
`live_stream_event_hashed_id`	No	The unique alphanumeric identifier for the live stream event associated with this channel episode.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv3.0.0Oct 7, 2026

addedInput schema / $defs

Added value: +{
+  "podcast_settings": {
+    "description": "Podcast specific settings for a channel episode. These settings only take effect\nif podcasting is enabled for the channel.\n",
+    "properties": {
+      "episode_number": {
+        "description": "The number of the episode.",
+        "type": [
+          "integer",
+          "null"
+        ]
+      },
+      "episode_type": {
+        "description": "The type of episode.",
+        "oneOf": [
+          {
+            "enum": [
+              "full",
+              "trailer",
+              "bonus"
+            ],
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "unevaluatedProperties": false
+      },
+      "explicit_content": {
+        "description": "Whether the episode contains explicit content.",
+        "type": "boolean"
+      },
+      "hide_from_feed": {
+        "description": "Whether to hide the episode from the podcast feed.",
+        "type": "boolean"
+      },
+      "season_number": {
+        "description": "The season number of the episode.",
+        "type": [
+          "integer",
+          "null"
+        ]
+      }
+    },
+    "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 / podcast_settings / $ref
```
Added value: +"#/$defs/podcast_settings"
```

removedInput schema / properties / payload / properties / podcast_settings / description

Removed value: -"Podcast specific settings for a channel episode. These settings only take effect\nif podcasting is enabled for the channel.\n"

removedInput schema / properties / payload / properties / podcast_settings / properties

Removed value: -{
-  "episode_number": {
-    "description": "The number of the episode.",
-    "type": [
-      "integer",
-      "null"
-    ]
-  },
-  "episode_type": {
-    "description": "The type of episode.",
-    "oneOf": [
-      {
-        "enum": [
-          "full",
-          "trailer",
-          "bonus"
-        ],
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "unevaluatedProperties": false
-  },
-  "explicit_content": {
-    "description": "Whether the episode contains explicit content.",
-    "type": "boolean"
-  },
-  "hide_from_feed": {
-    "description": "Whether to hide the episode from the podcast feed.",
-    "type": "boolean"
-  },
-  "season_number": {
-    "description": "The season number of the episode.",
-    "type": [
-      "integer",
-      "null"
-    ]
-  }
-}

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

removedInput schema / properties / podcast_settings / description

Removed value: -"Podcast specific settings for a channel episode. These settings only take effect\nif podcasting is enabled for the channel.\n"

removedInput schema / properties / podcast_settings / properties

Removed value: -{
-  "episode_number": {
-    "description": "The number of the episode.",
-    "type": [
-      "integer",
-      "null"
-    ]
-  },
-  "episode_type": {
-    "description": "The type of episode.",
-    "oneOf": [
-      {
-        "enum": [
-          "full",
-          "trailer",
-          "bonus"
-        ],
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "unevaluatedProperties": false
-  },
-  "explicit_content": {
-    "description": "Whether the episode contains explicit content.",
-    "type": "boolean"
-  },
-  "hide_from_feed": {
-    "description": "Whether to hide the episode from the podcast feed.",
-    "type": "boolean"
-  },
-  "season_number": {
-    "description": "The season number of the episode.",
-    "type": [
-      "integer",
-      "null"
-    ]
-  }
-}

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

First observedv2.0.0Oct 2, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Beyond annotations that already mark this as destructive, non-idempotent, and open-world, the description adds concrete operational context: required API token permissions, delegated permission behavior, the confirm=true requirement, and side effects including sharing access, notifying people, and incurring provider charges. These details materially help an agent understand authorization and consequence boundaries.

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?

The description is front-loaded with the purpose and then uses headings and a code block to organize permissions, confirm behavior, and side effects. It is appropriately sized for a complex mutation tool, though the permission text is somewhat verbose and could be tightened.

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?

Given 14 parameters, a nested object, no output schema, and rich annotations, the description covers the most important non-schema context: permissions, confirm requirement, and side effects. It does not describe return values or non-idempotency explicitly, but annotations already signal the latter and the schema covers fields, so the overall definition is nearly complete.

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 93%, so parameter meaning is already well documented in the input schema. The description reinforces the confirm requirement but does not add new semantics for the other 13 parameters, including nested podcast_settings or payload versus payload_file usage. This is the expected baseline when the schema carries nearly all parameter documentation.

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?

The description states a specific verb and resource: 'Updates an existing channel episode in a channel.' This clearly distinguishes the tool from create_channel_episode and delete_channel_episode by scope, but it does not explicitly name alternatives or contrast with sibling update tools like update_media or publish_channel_episode.

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?

Usage is implied by 'Updates an existing channel episode' and reinforced by 'Requires confirm=true for the requested mutation,' but the description does not state when to use this instead of related tools such as publish_channel_episode, un_publish_channel_episode, or update_channel. No explicit exclusions or alternative-routing guidance is provided.

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

Deploy Server