WebinarIgnition

Change access, users or page routing of a webinar

wi_change_advanced_settings

Destructive

Changes one group of the advanced settings of a campaign: protected access, the WordPress side, extra hosts and support addresses, which page the registration, thank-you, live, replay or closed view uses, the field names an email provider expects, or the wording of the privacy checkbox. Take it when access or a page address should change: "Only people from my list should get in." It needs the session, the webinar, the group, the fields and a clear yes from you, because it writes on your site and a member entry also creates a WordPress user with access. Read the current state first and say what changes. Only the group you name changes, and an unknown key refuses that whole group. Side effect: it acts on your connected WordPress site; nothing else is touched. Words hosts use: protect webinar, access only for my list, change page, extra host, privacy checkbox

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": {
      "group": "<group>",
      "settings": "<settings>"
    },
    "name": "wi_change_advanced_settings"
  }
}

Input Schema

Name	Required	Description
`site`	No	Which connected site is meant when this chat has more than one: the address exactly as wi_get_connector_status lists it under sites. Leave it out while only one site is connected.
`group`	Yes	Which group to change. One group per call.
`confirm`	No	Must be true, set only after the host said what may change, including any user this creates.
`settings`	Yes	The fields of that group with their new values, as wi_get_webinar_settings names them. Only passed keys change.
`session_id`	No	From an earlier turn (weiter · texte · stand).
`webinar_id`	No	The webinar (campaign) id, as wi_list_webinars returned it. Never invent an id.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

addedInput schema / properties / site

Added value: +{
+  "description": "Which connected site is meant when this chat has more than one: the address exactly as wi_get_connector_status lists it under sites. Leave it out while only one site is connected.",
+  "type": "string"
+}

AddedOct 26, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, non-idempotent and non-read-only, so the mutation and external-site framing is partly pre-supplied. The description still adds real value beyond them: the confirm gate, that a member entry creates a WordPress user with access, that only the named group changes, and that an unknown key rejects the whole group.

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?

Front-loaded with the purpose, but it drifts into repetition ("it writes on your site" then again "it acts on your connected WordPress site") and ends with a keyword dump ("Words hosts use: ...") that pads rather than informs.

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?

With a full schema, an output schema and rich annotations, the description covers the remaining gaps an agent needs: the confirm requirement, the site-level side effect, and group-scoped partial updates. Return value details are rightly omitted since an output schema exists.

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?

With 100% schema coverage the baseline is 3, but the description adds semantics not in the schema: partial-update behavior per group and the all-or-nothing rejection on an unknown key. The confirm and group concepts are reinforced rather than newly explained, so it stops short of 5.

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 ("Changes one group of the advanced settings of a campaign") and enumerates the groups covered (protected access, WordPress side, hosts/support, page routing, provider field names, privacy checkbox). An agent can tell it apart from wi_change_webinar_settings and wi_change_registration_fields by the group framing, though no sibling is named explicitly.

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 a concrete trigger ("Take it when access or a page address should change") with a quoted host phrasing, plus a prerequisite ("Read the current state first and say what changes"). No explicit when-not or named alternative tool, which keeps it short of a 5.

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

All WebinarIgnition tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.