Wistia MCP Server

Update Brand

update_brand

Destructive

Modify a Wistia brand's logos, colors, fonts, and styling; only sent fields change, and null clears them. Changes propagate to all content using the brand.

Instructions

Updates a brand. Only the fields you send are changed; send an explicit null to unset one. Renaming the account-level default brand is ignored : its name is managed by Wistia.

Changes propagate to everything the brand is applied to.

Requires api token with one of the following permissions

All data

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
`name`	No	The brand's display name. Renaming the account-level default brand is ignored; its name is managed by Wistia.
`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.
`brand_id`	Yes	The id of the brand
`page_logo`	No	The brand logo used for pages. `url` must be a Wistia delivery URL — see the note on uploading below. On accounts without custom branding the player logo is ignored, but the page logo is always applied.
`player_logo`	No	The brand logo used for the player. `url` must be a Wistia delivery URL — see the note on uploading below. Ignored on accounts whose plan doesn't include custom branding.
`payload_file`	No	Regular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
`border_radius`	No	The border radius in pixels for rounded corners.
`primary_color`	No	The primary brand color, used for primary buttons and the player playbar. Either a hex color string or a gradient represented as an array of [hexColor, percentage] tuples.
`contrast_icons`	No	Controls whether the player icon color is always white or uses an accessible contrast color when necessary.
`opaque_controls`	No	Controls the opacity of the video player control bar and big play button.
`body_font_family`	No	The brand font family for body text.
`button_font_family`	No	The brand font family for buttons.
`headline_font_family`	No	The brand font family for headlines.
`page_background_color`	No	The brand color used for page backgrounds. Either a hex color string or a gradient represented as an array of [hexColor, percentage] tuples.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Oct 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructive/non-idempotent/open-world, so the description is not carrying the safety burden alone. It adds real value beyond them: partial-update semantics, null-to-unset behavior, the ignored default-brand rename, propagation of changes to everything the brand is applied to, and the confirm=true gate. The trailing 'may share access, notify people or incur provider charges' is generic boilerplate that dilutes it slightly.

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-loads the operation and its key semantics in the first two sentences, then moves to permissions. The permissions block and the generic action-caveat sentence add bulk but the useful information is not buried.

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 mutation tool with no output schema but full schema description coverage and annotations, the description covers the mutation contract, the ignored-field edge case, propagation, auth requirements, and the confirm gate. Only an explicit note on return value/response shape is absent, which is minor given the annotation profile.

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 description coverage is 100%, so the baseline is 3; the description rises above it by explaining the cross-cutting mutation contract (only sent fields change, explicit null unsets) that governs all 16 parameters and is not spelled out per-field. Field-specific meaning is left entirely to the schema, which is acceptable at full coverage.

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 ('Updates a brand') and immediately narrows scope with partial-update semantics ('Only the fields you send are changed'). An agent can distinguish it from get_brand, delete_brand, create_brand and apply_brand from the name plus first sentence.

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?

Provides useful conditional rules (send explicit null to unset; renaming the default brand is ignored) and a prerequisite (confirm=true), but never states when to choose this tool over siblings like apply_brand, update_brand_preload, or update_customizations. Usage is implied rather than routed.

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

Deploy Server