Wistia MCP Server

Create Folder

create_folder

Destructive

Create a new Wistia folder with configurable name, description, public access, admin owner, and personal Library placement.

Instructions

Creates a new folder (previously called project). If the folder is created successfully the Location HTTP header will point to the new folder.

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.

An expiring access token created with the all:delegate_to_contact_permissions scope and an account authorization granting the create-folders permission can also be used. The folder's creator is the contact behind the token (the account owner for a token minted from an account-level token); adminEmail selects the folder's administrator (defaults to the account owner). personalLibrary creates the folder inside the My Library of the contact behind the token. The new folder is not covered by the token that created it, so follow-up requests need a token whose authorizations name the returned hashed id. Requires confirm=true for the requested mutation. May share access, notify people or incur provider charges.

Input Schema

Name	Required	Description
`name`	No	The name of the folder you want to create.
`public`	No	A flag indicating whether or not the folder is enabled for public access.
`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.
`adminEmail`	No	The email address of the person you want to set as the owner of this folder. Defaults to the Wistia Account Owner.
`description`	No	The folder’s description.
`payload_file`	No	Regular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
`personalLibrary`	No	When true, creates the folder inside the requesting user's personal "My Library" (owned by them) instead of a shared account folder.
`anonymousCanUpload`	No	Whether anonymous users can upload media to the folder.
`anonymousCanDownload`	No	Whether anonymous users can download media from the folder.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.0.0Oct 7, 2026

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."

First observedv2.0.0Oct 2, 2026

TDQS

A3.8/5.0

Behavior5/5

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

Annotations already flag this as a non-read-only, non-idempotent, destructive, open-world write, but the description adds substantial behavior beyond them: the Location header on success, the creator/admin defaults, that the new folder is not covered by the creating token, and confirmation that the mutation may share access, notify people, or incur charges.

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?

The purpose is correctly front-loaded, but the body is a dense block mixing an unformatted header line with several long sentences, and closes with generic boilerplate ("may share access, notify people or incur provider charges") that is vague rather than actionable. The authentication detail is valuable but could be tighter.

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, zero-required-parameter 11-param mutation with no output schema, the description covers the important gaps: success signal (Location header), permission requirements, confirm requirement, and the follow-up token caveat. Only the routing vs sibling creation tools is left unaddressed.

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% for all 11 parameters, so the schema already documents name, public, adminEmail, personalLibrary, anonymous upload/download, and the payload/payload_file alternatives. The description restates a few of these (adminEmail default, personalLibrary behavior) but adds no format or interaction detail the schema lacks, so baseline 3 applies.

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 first sentence gives a specific verb and resource ("Creates a new folder") and usefully notes the resource was previously called a project, which helps with naming drift. However, it never distinguishes itself from close siblings like create_subfolder or copy_folder, leaving the agent to infer which creator applies.

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 context is limited to authorization and mechanics: which token permissions are accepted, delegation scope, and the requirement that confirm=true be set for the mutation. There is no guidance on when to prefer this over create_subfolder or how folder vs subfolder creation differ, so alternative selection is left implicit.

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

Deploy Server