Skip to main content
Glama

WebinarIgnition

wi_webinar

Plan, write, and set up WordPress webinars from chat: generate topics, titles, invite emails, reminders, registration pages, and live or evergreen rooms, plus answer product questions.

Instructions

Plan, write and set up a webinar from a chat, and answer questions about WebinarIgnition. It picks a topic, produces the title, the invitation emails, the reminders and the registration page, and prepares the live, automated or evergreen room on the user's own WordPress site. Needs no sign-in. Returns JSON. was selects the step: • start — entry point; returns a question with tappable options. • thema — starts a conversation from the user's text; needs text. • weiter — continues a conversation; needs session_id and text. A result with ready=true means the texts can be written next with was=texte. • texte — writes the finished texts for a ready session; needs session_id. Optional: job_id to poll a running job, direction for an angle, skip_direction, invite_type (list, personal, facebook, whatsapp, instagram, linkedin, telegram, youtube), or type="custom" with custom_channel for any other channel. • stand — returns what the session has collected so far; needs session_id. • seite — checks a WordPress address for WebinarIgnition; needs url; returns state, next_action and next_url. • verbinden — connects the chat to the user's own WordPress; the first call needs session_id and url and returns a connect_url that the user opens in their own browser; a later call without url reports whether it went through. • faehigkeiten — lists the abilities of the connected site; needs session_id. • ausfuehren — runs one ability on the connected site; needs session_id, tool and args. Destructive abilities are not run here; the answer points to wi_webinar_delete. • trennen — drops the connection; needs session_id. • handoff — returns a handover link carrying the collected data; needs session_id (or known_facts/content), optional url. • technik — returns the setup plan without a connected site. • frage — answers a product question (prices, limits, integrations); needs text. • status — technical state of the connector. Returns { error, message } when a required field is missing, and { question } when the user has choices to make.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoThe WordPress address (seite). With was=handoff: the host's WordPress address to point the handover link at.
wasYesWhich step to run.
argsNoOnly with was=ausfuehren: the arguments for that ability, shaped by its input_schema.
textNoWhat the host said (thema · weiter) or the question in the host's language (frage).
toolNoOnly with was=ausfuehren: the ability name exactly as was=faehigkeiten reported it, e.g. webinarignition_create_webinar. Slashes and hyphens are accepted too, but the site publishes underscores.
typeNoOnly with was=texte: invites (default), starter, or custom. custom = the invitation is for a channel that is NOT one of the eight built-in platforms — pass the channel name in custom_channel. A channel outside the eight built-ins is written as custom, not as one of the eight.
focusNoOnly with was=start: what it should be about.
wantsNoOnly with was=start: what the host wants, as short keywords (e.g. "thema", "texte", "technik").
has_wiNoOnly with was=start: true when WebinarIgnition is already installed on the host's site.
job_idNoOnly with was=texte: the job number from an earlier call, to check whether the texts are ready. Without job_id a new job is started; only one text job runs at a time.
ratingNoOnly with was=handoff: the host's rating (1-10), if any.
contentNoOnly with was=handoff: finished text to carry over, if the session alone does not hold it.
has_mcpNoOnly with was=start: true when the host already uses an MCP/connector — the connector normally sets this itself.
languageNoThe language the host writes in.de
directionNoOptional with was=texte: the angle/framing of the invitation (natural language), e.g. 'Zeitersparnis und Skalierung ohne neue Mitarbeiter' for an agency. If missing, the invitation is written at once without a special angle.
situationNoOnly with was=start: what the host just said.
session_idNoFrom an earlier turn (weiter · texte · stand).
invite_typeNoOnly with was=texte, when the invitation is for a specific platform: list = email list, personal = personal message, facebook = Facebook post, whatsapp = WhatsApp status, instagram = Instagram post, linkedin = LinkedIn post, telegram = Telegram channel, youtube = YouTube post.
known_factsNoEverything you already know — send it every turn so nothing is lost on a restart.
has_wordpressNoOnly with was=start: true when the host already has a WordPress site.
custom_channelNoOnly with was=texte and type="custom": the exact name of the channel or format the invitation is for when it is not one of the eight built-in platforms — e.g. Xing, WeChat, Line, KakaoTalk, Viber, Threads, Mastodon, a guest article, or the host's own format. The text is then written for exactly this channel, not for a built-in platform.
skip_directionNoOnly with was=texte: true when the host wants NO special angle — then it generates without an angle.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behaviors: no sign-in required, JSON returns, error and question response shapes, the two-phase verbinden flow, the ready=true handoff between steps, and the single-running-text-job constraint. It adds substantive behavioral context without contradicting the annotations.

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

Conciseness5/5

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

The description is long but densely packed and well-structured: a one-sentence overview, then a scannable bullet list for each 'was' step. Every clause earns its place, and the front-loaded summary helps the agent orient before diving into the state details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 22-parameter, 14-state tool, the description is unusually complete: it covers entry points, continuation, text generation, WordPress connection, capability execution, disconnection, handoff, fallback planning, product questions, and status. The presence of an output schema further reduces the need to describe return values, though the description already covers the main response shapes.

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?

Schema coverage is 100%, so the baseline is 3. The description adds value above the schema by explaining step-specific dependencies, the intended state-machine flow, the custom-channel rule, and how job_id polling works. It does not merely repeat schema text; it organizes the parameters into a usable workflow.

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?

The description names a specific verb-resource pairing: plan, write, and set up a webinar, and answer WebinarIgnition questions. It clearly distinguishes from the only sibling, wi_webinar_delete, by stating that destructive abilities are not run here and the answer points to the delete tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The 'was' state machine gives explicit when-to-use guidance for each step, including required and optional parameters. It also provides an exclusion rule: destructive abilities are not executed here and route to wi_webinar_delete. This is actionable selection guidance, not just a summary.

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