Skip to main content
Glama
Sign In
Wistia MCP Server

Wistia MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create Webinar

create_webinar
Destructive

Create a Wistia webinar by providing its title, scheduled start time, duration, and time zone; confirm the action to save it.

Instructions

Creates a new 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_webinar"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoThe title of the webinar
accountNoNamed private Wistia account; selects credentials, not a remote account ID.
confirmNoSet true only when the user asked for exactly this action.
payloadNoComplete JSON request body instead of body flags. Supports current nested customization, caption and nullable values.
folder_idNoHashed ID of the folder to place this webinar in. Defaults to the account's default webinar folder if not provided.
time_zoneNoThe IANA time zone identifier the webinar is scheduled in.
descriptionNoThe description of the webinar
payload_fileNoRegular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
scheduled_forNoThe scheduled start time as a UTC formatted ISO 8601 string (offset `Z` or `+00:00`).
event_durationNoDuration of the event in minutes (minimum 15)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • 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."
  2. First observedv2.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the annotations (which already flag destructive=true and openWorld=true), the description adds real behavioral context: the required token scope, delegation behavior via all:delegate_to_contact_permissions, the confirm=true gate, and side-effect warnings ('may share access, notify people or incur provider charges'). Idempotency and concrete return behavior are not covered, so it stops short of a 5.

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 is front-loaded in the first sentence and the permission/side-effect details follow in a clearly separated section. It is somewhat verbose, especially the multi-line permission block, but the content is relevant and earns its place.

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 10-parameter mutation with a nested object and no output schema, the description covers the important non-schema concerns: auth scope, the confirm gate, and charge/notification side effects. Return values need not be explained without an output schema, and parameter detail is fully carried by the schema.

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 including the nested payload is already documented in the schema. The description adds no parameter-level syntax or format detail (e.g., the payload vs payload_file vs body-flag mutual exclusivity), so the baseline 3 applies.

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?

The description opens with a specific verb+resource: 'Creates a new webinar.' That cleanly identifies it among the many webinar siblings (get_webinar, update_webinar, delete_webinar). However, it does not explicitly name or contrast with those siblings, so it earns a 4 rather than 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 Guidelines2/5

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

The description states preconditions (required token permissions, confirm=true) but gives no guidance on when to choose this tool versus alternatives such as update_webinar or create_webinar_registration. There are no exclusions or context cues for selection, leaving the agent to infer usage.

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

Deploy Server

Other Tools