Wistia MCP Server

Create Channel Episode

create_channel_episode

Destructive

Adds a new episode to a Wistia channel using a media ID, with title, summary, publish status, and podcast settings. Use it to publish, schedule, or draft channel content.

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

TableJSON 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	Must be true for the specific user-requested write.
`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	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.'
`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	Podcast specific settings for a channel episode. These settings only take effect if podcasting is enabled for the channel.
`channel_hashed_id`	Yes	The hashed ID of the channel to add the episode to.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Oct 2, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare openWorldHint=true, destructiveHint=true, idempotentHint=false, but the description adds genuine context beyond them: required token permission scopes, the delegation scope, the confirm=true requirement for the mutation, and side effects ('May share access, notify people or incur provider charges'). This is meaningful behavioral disclosure.

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 purpose is front-loaded in the first sentence, followed by structured permission and mutation requirements. The permission markdown block is somewhat heavy, but it is relevant given the authentication complexity and earns its space.

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 destructive mutation with a nested payload and no output schema, the description covers permissions, the confirm requirement, and side-effect warnings well. It does not describe the post-creation return behavior, but with no output schema this is a minor gap.

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%, so the schema already documents all 12 parameters including the nested payload and podcast_settings. The description adds no parameter-level detail beyond mentioning confirm=true, so the baseline of 3 is appropriate.

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 opens with a specific verb+resource: 'Creates a new channel episode in a channel.' This clearly states what the tool does and is not a tautology of the title. However, it offers no differentiation from related siblings such as create_channel, update_channel_episode, 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 Guidelines2/5

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

There is no explicit when-to-use guidance or comparison to alternatives like create_channel, publish_channel_episode, or update_channel_episode. The confirm=true and permission notes describe how to invoke but not when this tool is the right choice over its siblings.

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

Deploy Server