WebinarStack

Publish Widget

webinarstack.webinars.widget_style_publish

Idempotent

Publish the widget draft to the live widget and refresh its CDN snapshot. Publishing copies the whole widget draft, including any unpublished editor changes to its content, to the live widget, exactly like the editor's Publish button. For about 45 to 60 seconds after each publish or branding change, the live modal chrome can briefly wrap the previous form while the CDN snapshot refreshes; it heals on its own. Last write wins. Responses include updatedAt. An editor tab that is open on this widget can autosave over a draft written through the API. This changes the widget's style object only. It is not page-builder authoring: it cannot add, remove or edit blocks or form fields.

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": {
      "webinarId": "<webinarId>"
    },
    "name": "webinarstack.webinars.widget_style_publish"
  }
}

Input Schema

Name	Required	Description	Default
`webinarId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Discloses behavior well beyond the annotations: a 45–60 second CDN refresh window where modal chrome can briefly wrap the previous form, last-write-wins conflict semantics, inclusion of updatedAt in responses, and an autosave race from open editor tabs. Annotations only say readOnly=false, idempotent=true, destructive=false; the description adds the timing and race hazards they omit.

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 core action and CDN refresh, then layers caveats about timing, conflicts, and scope. It is dense with several clauses, but each sentence contributes distinct behavioral information rather than restating the name.

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 single-parameter, no-output-schema publish tool, it covers timing quirks, conflict resolution, autosave races, and scope limitations. Only minor details like required permissions or error behavior are absent.

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?

The sole parameter webinarId has 0% schema description coverage, and the description does not add meaning about it. However, it is a simple required UUID identifier whose semantics are largely self-evident, so the gap is minor and a baseline 3 is appropriate.

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 and resource — it publishes the widget draft to the live widget and refreshes the CDN snapshot. It clearly distinguishes itself from sibling widget_style_get/update by describing the copy-from-draft semantics and explicitly ruling out page-builder authoring.

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?

Explains the action is equivalent to the editor's Publish button, including that it carries unpublished editor changes. It gives a clear 'what this is not' boundary (cannot add, remove, or edit blocks or form fields) but does not explicitly name an alternative sibling tool for the blocked use case.

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

All WebinarStack 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.

Resources

Need Help?