Wistia MCP Server

Update Webinar

update_webinar

Destructive

Modify an existing Wistia webinar's title, schedule, time zone, description, folder, or duration.

Instructions

Updates an existing webinar.

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

Name	Required	Description
`id`	Yes	The hashed ID of the webinar
`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.
`webinar`	No
`payload_file`	No	Regular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv3.0.0Oct 7, 2026

addedInput schema / $defs

Added value: +{
+  "webinar": {
+    "properties": {
+      "description": {
+        "description": "The description of the webinar",
+        "type": "string"
+      },
+      "event_duration": {
+        "description": "Duration of the webinar in minutes (minimum 15)",
+        "minimum": 15,
+        "type": "integer"
+      },
+      "folder_id": {
+        "description": "Hashed ID of the folder to move this webinar to. Can only be changed before the webinar has started.",
+        "type": "string"
+      },
+      "scheduled_for": {
+        "description": "The scheduled start time as a UTC formatted ISO 8601 string (offset `Z` or `+00:00`).",
+        "format": "date-time",
+        "type": "string"
+      },
+      "time_zone": {
+        "description": "The IANA time zone identifier the webinar is scheduled in.",
+        "type": "string"
+      },
+      "title": {
+        "description": "The title of the webinar",
+        "type": "string"
+      }
+    },
+    "type": "object",
+    "unevaluatedProperties": false
+  }
+}

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 / webinar / $ref
```
Added value: +"#/$defs/webinar"
```

removedInput schema / properties / payload / properties / webinar / properties

Removed value: -{
-  "description": {
-    "description": "The description of the webinar",
-    "type": "string"
-  },
-  "event_duration": {
-    "description": "Duration of the webinar in minutes (minimum 15)",
-    "minimum": 15,
-    "type": "integer"
-  },
-  "folder_id": {
-    "description": "Hashed ID of the folder to move this webinar to. Can only be changed before the webinar has started.",
-    "type": "string"
-  },
-  "scheduled_for": {
-    "description": "The scheduled start time as a UTC formatted ISO 8601 string (offset `Z` or `+00:00`).",
-    "format": "date-time",
-    "type": "string"
-  },
-  "time_zone": {
-    "description": "The IANA time zone identifier the webinar is scheduled in.",
-    "type": "string"
-  },
-  "title": {
-    "description": "The title of the webinar",
-    "type": "string"
-  }
-}

removedInput schema / properties / payload / properties / webinar / type
```
Removed value: -"object"
```
removedInput schema / properties / payload / properties / webinar / unevaluatedProperties
```
Removed value: -false
```
addedInput schema / properties / webinar / $ref
```
Added value: +"#/$defs/webinar"
```

removedInput schema / properties / webinar / properties

Removed value: -{
-  "description": {
-    "description": "The description of the webinar",
-    "type": "string"
-  },
-  "event_duration": {
-    "description": "Duration of the webinar in minutes (minimum 15)",
-    "minimum": 15,
-    "type": "integer"
-  },
-  "folder_id": {
-    "description": "Hashed ID of the folder to move this webinar to. Can only be changed before the webinar has started.",
-    "type": "string"
-  },
-  "scheduled_for": {
-    "description": "The scheduled start time as a UTC formatted ISO 8601 string (offset `Z` or `+00:00`).",
-    "format": "date-time",
-    "type": "string"
-  },
-  "time_zone": {
-    "description": "The IANA time zone identifier the webinar is scheduled in.",
-    "type": "string"
-  },
-  "title": {
-    "description": "The title of the webinar",
-    "type": "string"
-  }
-}

removedInput schema / properties / webinar / type
```
Removed value: -"object"
```
removedInput schema / properties / webinar / unevaluatedProperties
```
Removed value: -false
```

First observedv2.0.0Oct 2, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds real value beyond that: required token permission scopes, delegation semantics, the confirm=true requirement, and side effects ('may share access, notify people or incur provider charges').

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The one-line purpose is front-loaded well, but the large fenced permission block and delegation paragraph dominate the text and read as templated boilerplate. It is not bloated relative to necessity, but the signal-to-noise ratio is only moderate.

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 6-parameter mutation tool with a nested webinar object and no output schema, the description adequately covers auth, the confirm requirement, and side effects. It does not touch on the conditional field restrictions (e.g., folder_id) that the schema carries, but overall it is complete enough to invoke correctly.

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 coverage is 83%, so the schema already documents most inputs, including the per-field webinar properties. The description adds a bit of meaning for the confirm flag but says nothing about the payload/payload_file alternatives or the id parameter. Baseline 3 is appropriate when the schema does the heavy lifting.

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 an existing webinar'), which is clear on its own. It does not explicitly distinguish itself from create_webinar, delete_webinar, or get_webinar, relying on the verb to imply the difference. Clear but without active sibling differentiation.

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?

The description implies usage ('updates an existing webinar') and states a precondition (confirm=true for the mutation), but never says when to choose this over create_webinar or delete_webinar, nor what kinds of edits are appropriate. Usage is implied rather than spelled out.

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

Deploy Server