Wistia MCP Server

Copy Media

copy_media

Destructive

Copy a Wistia media item and its assets to a destination folder, defaulting to the source folder, with optional new owner. Requires confirm=true to perform the write.

Instructions

This endpoint copies a media and its assets to a destination folder (defaults to source media).

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
`owner`	No	An email address specifying the owner of the new media. Defaults to the source media’s current owner if omitted or invalid.
`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.
`folder_id`	No	The ID of the folder where you want the new copy placed. Defaults to the source media’s current folder if omitted or invalid.
`payload_file`	No	Regular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
`media_hashed_id`	Yes	The hashed ID of the media.

Schema Changelog

Changes observed during successful MCP inspections.

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 cover the safety profile (destructiveHint=true, readOnlyHint=false, idempotentHint=false). The description adds valuable non-annotated context: the required permission scopes, delegate_to_contact_permissions semantics, the confirm=true requirement, and side effects like sharing access, notifying people, or incurring provider 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 opening sentence is front-loaded and clear, but the permission block and scope details are verbose and mix prose with a code-fenced permission name. Reasonably sized but 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?

Covers the mutation, its side effects, auth scopes, and the confirm requirement for a write tool with no output schema. Given 7 params and a nested payload object, this is largely complete, though it doesn't clarify the owner/account selection nuances beyond what the schema states.

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% and the schema itself documents all parameters including nested payload properties, so the baseline is 3. The description adds the confirm=true constraint which reinforces what the schema says but doesn't extend it further.

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?

States a specific verb+resource ('copies a media and its assets') and names the destination behavior (defaults to source folder). Doesn't explicitly differentiate from sibling bulk_copy_media, move_media, or swap_media, so an agent could confuse which copy variant to use.

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?

Describes the operation context (copies to a destination folder) and includes permission requirements, but gives no explicit when-to-use vs when-not-to guidance or alternatives like bulk_copy_media or move_media. Usage is implied by the copy semantics rather than stated.

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

Deploy Server