Wistia MCP Server

Create Channel Episode

create_channel_episode

Destructive

Create a new episode in a Wistia channel by specifying media, title, description, publish status, scheduling, and podcast settings.

Instructions

Creates a new 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.
`media_id`	No	The alphanumeric hashed ID of the media to be added as a channel episode.
`publish_at`	No
`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.
`publish_status`	No	The status of whether or not the episode has been published to your channel.
`podcast_settings`	No
`channel_hashed_id`	Yes	The hashed ID of the channel to add the episode to.

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 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
+  },
+  "publish_at": {
+    "description": "The date and time when the episode should be published in UTC timezone. Required when publish_status is 'scheduled'. Must be a valid ISO8601 timestamp in UTC (ending with 'Z').  Can only be provided when publish_status is 'scheduled.'",
+    "format": "date-time",
+    "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 / 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 / payload / properties / publish_at / $ref
```
Added value: +"#/$defs/publish_at"
```

removedInput schema / properties / payload / properties / publish_at / description

Removed value: -"The date and time when the episode should be published in UTC timezone. Required when publish_status is 'scheduled'. Must be a valid ISO8601 timestamp in UTC (ending with 'Z').  Can only be provided when publish_status is 'scheduled.'"

removedInput schema / properties / payload / properties / publish_at / format
```
Removed value: -"date-time"
```
removedInput schema / properties / payload / properties / publish_at / type
```
Removed value: -"string"
```
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
```
addedInput schema / properties / publish_at / $ref
```
Added value: +"#/$defs/publish_at"
```

removedInput schema / properties / publish_at / description

Removed value: -"The date and time when the episode should be published in UTC timezone. Required when publish_status is 'scheduled'. Must be a valid ISO8601 timestamp in UTC (ending with 'Z').  Can only be provided when publish_status is 'scheduled.'"

removedInput schema / properties / publish_at / format
```
Removed value: -"date-time"
```
removedInput schema / properties / publish_at / type
```
Removed value: -"string"
```

First observedv2.0.0Oct 2, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and non-idempotency, so the safety bar is partly covered. The description goes further by naming the exact permission scopes required, the confirm=true gate, and concrete side effects ('may share access, notify people or incur provider charges') — useful context beyond the annotations.

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

Conciseness3/5

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

Purpose is front-loaded and the markdown headers structure the requirements, but the permission boilerplate occupies most of the text while the genuinely decision-relevant facts (confirm=true, charges/notifications) are pushed to the end.

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 12-parameter mutation with nested objects and no output schema, the description covers the important operational facts: authorization needs, the confirm gate, and side effects. The create-vs-sibling distinction is the main remaining gap, and the payload/payload_file mechanics are left to the schema.

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?

With 83% schema description coverage, the schema already documents nearly all parameters including the publish_at/podcast_settings constraints, so the baseline of 3 applies. The description adds no parameter-level detail of its own beyond the confirm flag.

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 ('Creates a new channel episode in a channel'), which is clear. It does not distinguish itself from nearby siblings like update_channel_episode, publish_channel_episode, or delete_channel_episode, so an agent gets the action but not the routing logic.

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?

It gives real prerequisites: the required token permission, the delegate-to-contact scope, and that confirm=true is needed for the mutation. However it never says when to choose this over publish_channel_episode or update_channel_episode, leaving the create-vs-alternative decision to inference.

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

Deploy Server