Wistia MCP Server

Update Brand Preload

update_brand_preload

Destructive

Set or clear an account's default page logo and update its default player color. Omit a field to keep it unchanged.

Instructions

Persists the account's default page logo (by Bakery hashed_id) and default player color. Both fields are optional independently : omit a field to leave that account setting untouched. Passing an empty string for selected_logo_hashed_id clears the logo.

Requires the OAuth contact to be an owner or manager of the account (or a Wistia admin) : mirrors the auth check on the underlying updateWtwBrandKitAccountSettings GraphQL mutation.

Deliberately narrower than the mutation: this endpoint does not create/update BrandKits or set body font family. Glass's onboarding customize step writes only these two fields; broader brand-kit editing continues to happen through the WTW web UI + GraphQL.

Requires api token with one of the following permissions

(any scope allowed)

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

Input Schema

TableJSON Schema

Name	Required	Description
`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.
`payload_file`	No	Regular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
`selected_player_color`	No	Hex color string (e.g. "#3366FF") for the account's default player color — 6 hex digits, with or without the leading `#`. Omit or send an empty string to leave the current color untouched (there is no clear operation — color always has a value). Malformed values are rejected at the API boundary; without this check, the model's sanitize step would return nil and silently reset the account color to the global default.
`selected_logo_hashed_id`	No	Bakery hashed_id of an uploaded logo image, which will become the account's default page logo. Omit to leave the current logo untouched. Pass an empty string to clear the logo.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Oct 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare destructive/non-idempotent/open-world, and the description adds material context beyond them: owner/manager-or-Wistia-admin auth requirement mirroring updateWtwBrandKitAccountSettings, the confirm=true gate, the empty-string clear semantics, and the silent-reset failure mode when the color sanitize step returns nil. These are real behavioral disclosures, not restatements.

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?

Front-loaded with what the tool writes, followed by optionality rules, auth, and scope limits in descending priority. The appended permissions block and minor repetition of the clear/omit rule cost some tightness, but every core sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation with 100% schema coverage and no output schema, the description covers the remaining gaps an agent needs: exactly which two fields are written, auth requirements, confirmation requirements, clearing behavior, and the deliberate scope ceiling. Nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description usefully consolidates the omit-vs-clear rule across both the top-level and nested duplicate parameters and notes there is no clear operation for color. This adds modest meaning over the schema, which already carries most of the field detail.

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

Purpose5/5

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

States a specific verb+resource (persists the account default page logo and default player color) and names exactly what is written. It explicitly distinguishes itself from the broader underlying mutation and from the rest of the brand-kit tooling, so an agent can separate it from siblings like update_brand, create_brand, and get_brand_preload without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear usage conditions: both fields optional independently, omit to leave untouched, empty string clears the logo, and broader brand-kit editing should go through the WTW web UI + GraphQL. It stops short of naming a specific sibling tool as the alternative, but the when/when-not boundary is well drawn.

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

Deploy Server