Wistia MCP Server

Purchase Captions

purchase_captions

Destructive

Purchase English captions for a Wistia media using a saved credit card. Requires confirmation and can order human-reviewed or automated captions.

Instructions

This method is for purchasing English captions for a media. The request will charge the credit card on the account if successful. A saved credit card is required to use this endpoint.

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
`rush`	No	Enable rush order for one business day turnaround instead of the standard four, for human-reviewed captions only. Rush bills at the account's higher per-minute rate.
`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.
`automated`	No	Order computer-generated captions or human-reviewed ones. What each costs depends on the account's plan and billing settings; computer-generated captions are included at no cost on some plans and billed per minute on others.
`payload_file`	No	Regular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
`media_hashed_id`	Yes	Unique identifier for the media.
`automatically_enable`	No	Automatically enable captions for the media once the order is ready or hold the captions for review before manually enabling.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Oct 2, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare destructive=true, openWorld=true, and non-idempotent behavior, but the description adds substantive context beyond them: it charges the account's credit card on success, requires a saved card, and specifies token permission scopes. It stops short of 5 because it doesn't cover failure/refund behavior or what the confirmation response returns.

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 and the billing side-effect are front-loaded in the first two sentences, which is exactly right for a purchase tool. The permission block is templated boilerplate and somewhat long, but it is relevant auth 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 destructive, charge-incurring mutation with a rich nested schema and no output schema, the description covers purpose, side effects, prerequisites, and auth. The main gap is that it doesn't note how to track the resulting order (e.g. via get_order_status), but nothing critical for invocation 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 every parameter (rush, automated, automatically_enable, payload, confirm, etc.) is already documented in the schema. The description adds no parameter-level meaning beyond that, making the baseline 3 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?

States a specific verb and resource: 'purchasing English captions for a media,' with the additional 'English' scope qualifier. An agent can tell this is a paid caption order rather than a caption-track edit. It never names or distinguishes itself from siblings like create_captions or create_bulk_purchase, so it stops short of a 5.

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?

It gives a real prerequisite (a saved credit card is required) and a required flag (confirm=true), which frame when this tool will work. However, it never says when to choose this over create_captions or how it relates to create_bulk_purchase, leaving the key routing decision 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