Wistia MCP Server

Update Brand Preload

update_brand_preload

Destructive

Set or clear a Wistia account's default page logo and update its default player color. Omit a field to leave it unchanged; use an empty logo ID to clear it.

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

Name	Required	Description
`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.
`payload_file`	No	Regular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
`selected_player_color`	No
`selected_logo_hashed_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedv3.0.0Oct 7, 2026

addedInput schema / $defs

Added value: +{
+  "selected_logo_hashed_id": {
+    "description": "Bakery hashed_id of an uploaded logo image, which will become the\naccount's default page logo. Omit to leave the current logo\nuntouched. Pass an empty string to clear the logo.\n",
+    "type": "string"
+  },
+  "selected_player_color": {
+    "description": "Hex color string (e.g. \"#3366FF\") for the account's default player\ncolor — 6 hex digits, with or without the leading `#`. Omit or send\nan empty string to leave the current color untouched (there is no\nclear operation — color always has a value). Malformed values are\nrejected at the API boundary; without this check, the model's\nsanitize step would return nil and silently reset the account color\nto the global default.\n",
+    "pattern": "^(#?[0-9a-fA-F]{6})?$",
+    "type": "string"
+  }
+}

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

addedInput schema / properties / payload / properties / selected_logo_hashed_id / $ref
```
Added value: +"#/$defs/selected_logo_hashed_id"
```

removedInput schema / properties / payload / properties / selected_logo_hashed_id / description

Removed value: -"Bakery hashed_id of an uploaded logo image, which will become the\naccount's default page logo. Omit to leave the current logo\nuntouched. Pass an empty string to clear the logo.\n"

removedInput schema / properties / payload / properties / selected_logo_hashed_id / type
```
Removed value: -"string"
```
addedInput schema / properties / payload / properties / selected_player_color / $ref
```
Added value: +"#/$defs/selected_player_color"
```

removedInput schema / properties / payload / properties / selected_player_color / description

Removed value: -"Hex color string (e.g. \"#3366FF\") for the account's default player\ncolor — 6 hex digits, with or without the leading `#`. Omit or send\nan empty string to leave the current color untouched (there is no\nclear operation — color always has a value). Malformed values are\nrejected at the API boundary; without this check, the model's\nsanitize step would return nil and silently reset the account color\nto the global default.\n"

removedInput schema / properties / payload / properties / selected_player_color / pattern
```
Removed value: -"^(#?[0-9a-fA-F]{6})?$"
```
removedInput schema / properties / payload / properties / selected_player_color / type
```
Removed value: -"string"
```
addedInput schema / properties / selected_logo_hashed_id / $ref
```
Added value: +"#/$defs/selected_logo_hashed_id"
```

removedInput schema / properties / selected_logo_hashed_id / description

Removed value: -"Bakery hashed_id of an uploaded logo image, which will become the\naccount's default page logo. Omit to leave the current logo\nuntouched. Pass an empty string to clear the logo.\n"

removedInput schema / properties / selected_logo_hashed_id / type
```
Removed value: -"string"
```
addedInput schema / properties / selected_player_color / $ref
```
Added value: +"#/$defs/selected_player_color"
```

removedInput schema / properties / selected_player_color / description

Removed value: -"Hex color string (e.g. \"#3366FF\") for the account's default player\ncolor — 6 hex digits, with or without the leading `#`. Omit or send\nan empty string to leave the current color untouched (there is no\nclear operation — color always has a value). Malformed values are\nrejected at the API boundary; without this check, the model's\nsanitize step would return nil and silently reset the account color\nto the global default.\n"

removedInput schema / properties / selected_player_color / pattern
```
Removed value: -"^(#?[0-9a-fA-F]{6})?$"
```
removedInput schema / properties / selected_player_color / type
```
Removed value: -"string"
```

First observedv2.0.0Oct 2, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare the safety profile (destructive, non-idempotent, open world), and the description adds substantial context beyond them: the exact auth requirement (owner or manager, or Wistia admin), the mutation it mirrors, the clear-on-empty-string behavior for the logo, and the absence of any color-clear operation.

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 action is front-loaded, and the optionality rule follows immediately. It is somewhat verbose with doubled colons and a trailing permissions/confirm boilerplate block that is generic rather than tool-specific, costing a point.

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 6-parameter mutation with no output schema, the description supplies the auth precondition, the scoping limits, the destructive clear behavior, and which underlying operation it mirrors. An agent has everything needed to call it correctly and interpret the effect.

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 67% and the $defs already document the omit/empty-string semantics, color pattern, and default-reset risk. The description largely restates the independent-optionality and clear-on-empty behavior that the schema already carries, adding little new parameter meaning.

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 and resource: persists the account's default page logo (by Bakery hashed_id) and default player color. It explicitly distinguishes itself from both the sibling read tool (get_brand_preload) and the broader underlying mutation, so an agent can tell what it does without opening the 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 context on field usage (omit to leave untouched, empty string clears the logo) and an explicit scope exclusion: it does not create/update BrandKits or set body font family, which continue through the WTW web UI + GraphQL. It stops short of naming a specific sibling tool as the alternative, which keeps it below a 5.

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

Deploy Server