Skip to main content
Glama
Sign In
Wistia MCP Server

Wistia MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Copy Media

copy_media
Destructive

Copies a Wistia media item and its assets to a destination folder, defaulting to the source folder, with optional new owner.

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "media_hashed_id": "<media_hashed_id>"
    },
    "name": "copy_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerNoAn email address specifying the owner of the new media. Defaults to the source media’s current owner if omitted or invalid.
accountNoNamed private Wistia account; selects credentials, not a remote account ID.
confirmNoSet true only when the user asked for exactly this action.
payloadNoComplete JSON request body instead of body flags. Supports current nested customization, caption and nullable values.
folder_idNoThe ID of the folder where you want the new copy placed. Defaults to the source media’s current folder if omitted or invalid.
payload_fileNoRegular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
media_hashed_idYesThe hashed ID of the media.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • 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."
  2. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare the safety profile (destructiveHint=true, idempotentHint=false, openWorldHint=true), and the description adds genuinely non-obvious context beyond that: the exact permission scopes required, delegated-token behavior, the confirm gate, and that the operation may share access, notify people, or incur provider charges. That is real added value, though it doesn't explain what specifically is destroyed or how the copy behaves on conflicts.

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 core purpose is front-loaded in the first sentence, followed by clearly chunked requirement blocks. The permission block is somewhat verbose, but each sentence carries operative information rather than filler.

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 7-parameter mutation with nested payload options and no output schema, the description covers auth, confirmation, and side effects adequately. It leaves the copy-vs-move-vs-bulk routing and any post-copy result expectations unaddressed, but nothing essential to invoking it correctly is missing.

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 parameters (owner, folder_id, account, confirm, payload variants, file payload) are already fully documented in the schema. The description adds only the default-destination nuance, which the schema also states, so it earns the baseline rather than more.

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 and resource — copies a media and its assets to a destination folder — with the default destination behavior given inline. It does not explicitly distinguish itself from close siblings like bulk_copy_media or move_media, but an agent can still tell what this single-item operation does.

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?

Useful context is given: the required permission scopes, the delegated-permission alternative, and the confirm=true requirement. However, it never says when to prefer this over bulk_copy_media or move_media, nor when not to use it, so routing between siblings is left 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

Other Tools