Skip to main content
Glama
Sign In
Wistia MCP Server

Wistia MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create Webinar Collaborator

create_webinar_collaborator
Destructive

Invite a webinar collaborator (producer) by email. Creates a contact if none exists; viewers cannot be collaborators.

Instructions

Invites a collaborator (producer) to a webinar by specifying their email address. Creates a new contact if one doesn't exist with that email. Note that viewers cannot be webinar collaborators.

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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "webinar_id": "<webinar_id>"
    },
    "name": "create_webinar_collaborator"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoEmail address of the contact to invite. Creates a new contact if one doesn't exist. Note that viewers cannot be webinar collaborators.
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.
webinar_idYesHashed ID of the webinar
payload_fileNoRegular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.

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

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint, openWorldHint, and non-idempotency, but the description adds substantial context beyond them: a new contact is created as a side effect if the email is unknown, specific token permission requirements are listed, delegate-token behavior is explained, and the confirm=true requirement and possible charges/notifications are disclosed. This is a rich behavioral profile, though some of the closing warnings read as generic boilerplate.

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 opening purpose sentence and the viewer constraint are well front-loaded, but the multi-line permission block is verbose template-style content that inflates the description, and the email side-effect is duplicated from the schema. Efficient in parts, padded in others.

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 mutating, nested-schema tool with annotations present and no output schema, the description covers the key gaps an agent needs: side effects, auth/permission requirements, the confirm gate, and collaborator eligibility. Only minor gaps (return behavior, relationship to sibling collaborator tools) remain.

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 the schema already documents email, account, confirm, payload, webinar_id, and payload_file. The description restates the email side effect but adds no syntax or format detail beyond the schema. 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.

Purpose5/5

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

States a specific verb+resource (invites a collaborator/producer to a webinar) via email, immediately distinguishing it from siblings like create_channel_collaborator and delete_webinar_collaborator. The scope constraint ('viewers cannot be webinar collaborators') further sharpens the intent.

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: use to invite a producer by email, requires confirm=true, and specifies viewers are excluded as collaborators. It does not explicitly route the agent against alternative siblings (e.g. invite_contacts or channel collaborators), so it stops short of full when/when-not guidance.

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