Skip to main content
Glama
thenavidm

Wistia MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create Channel

create_channel
Destructive

Creates a Wistia channel for organizing videos. Requires confirm=true and may share access, notify people, or incur charges.

Instructions

Creates a channel. Requires confirm=true for the requested mutation. May share access, notify people or incur provider charges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoThe display name for the channel
accountNoNamed private Wistia account; selects credentials, not a remote account ID.
confirmNoMust be true for the specific user-requested write.
payloadNoComplete JSON request body instead of body flags. Supports current nested customization, caption and nullable values.
custom_urlNoUse if embedding the channel on your own site. The custom URL ensures links always direct to your page and not Wistia's.
descriptionNoThe channel's description.
payload_fileNoRegular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
podcast_enabledNoWhether podcasting is enabled for this channel.
podcast_settingsNoPodcast specific settings for a channel. These settings only take effect if podcasting is enabled for the channel. These values appear in the channel's publicly accessible podcast RSS feed.
auto_publish_enabledNoWhether the episodes are automatically published when added to the channel. Cannot be enabled if podcasting is on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/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 idempotentHint=false, but the description adds real context beyond them: the confirm=true gate and side effects (sharing access, notifying people, incurring charges) that are nowhere in the schema. This is the strongest part of the definition.

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?

Two short sentences with no padding, and the precondition is front-loaded before the side-effect warning. Nothing here is expendable, though the brevity comes at the cost of coverage.

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 10-parameter tool with nested objects, the annotations carry the safety profile and the schema carries the parameter detail, so the description is adequate. It omits the mutually exclusive input modes (flags vs payload vs payload_file), which is the one gap an agent could stumble on.

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 10 parameters in detail. The description only touches the confirm parameter and adds no format or semantics beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Creates a channel" states a specific verb and resource, but it is essentially a restatement of the tool name and title, adding no scope or distinguishing detail. With siblings like create_brand and create_channel_episode present, nothing here separates this tool from the rest.

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 when-to-use guidance and no routing to or away from alternatives such as create_channel_episode or update_channel. The confirm requirement is a hard precondition rather than usage context, so an agent is left to infer when this tool applies.

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

Deploy Server

Other Tools