Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
wi_webinarA

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.

wi_webinar_deleteA

Delete or replace something on the connected WordPress site — irreversible. Runs only an ability that is verified as destructive: delete a campaign, a webhook, registrants (single or all), the logs, the attendee questions, or the HC import that replaces a campaign. Writes abilities are not run here; use wi_webinar with was="ausfuehren" for those. Needs session_id and tool, optional args. Returns JSON.

Prompts

Interactive templates invoked by user choice

NameDescription
build_my_webinarBuild a complete webinar — topic, title, invitation emails and registration page.
find_my_topicNot sure what to talk about? Find a webinar topic your audience is already looking for.
can_webinarignition_do_thisAsk anything about WebinarIgnition — integrations, limits, pricing, or whether it fits what you need.
write_my_invitationI already have a topic — write my invitation email and title.

Resources

Contextual data attached and managed by the client

NameDescription
Which interface to useWhich existing WordPress interface handles which job — and where an AI cannot edit (Elementor, Divi, Thrive).
What WebinarIgnition solvesVerified answers: integrations, webhooks, limits, licences, video sources, page builders, when it is not the right tool.
How WebinarIgnition worksWhat WebinarIgnition does, who you are building for, and how to run the conversation.

TDQS

A4.6/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: wi_webinar handles all non-destructive planning, setup, connection, and ability execution, while wi_webinar_delete is explicitly restricted to destructive deletion/replacement abilities. The boundary is reinforced by the description of wi_webinar, which points to wi_webinar_delete for destructive operations.

Naming Consistency4/5

Both tools share a consistent 'wi_webinar' prefix, which ties them to the domain. However, the main tool is named as a bare noun (wi_webinar) rather than following a verb_noun pattern like its counterpart (wi_webinar_delete), a minor deviation from ideal consistency.

Tool Count3/5

With only two tools for a broad domain (webinar planning, writing, WordPress connection, ability execution, deletion, Q&A, handoff), the surface feels thin. While consolidating many actions into a single parameterized tool is a valid design choice, the low count borders on under-provisioned.

Completeness4/5

The tools cover the full lifecycle: planning, content generation, site connection, running non-destructive abilities, destructive deletion/replacement, handoff, and technical status. Minor gaps exist (e.g., no explicit list or update tools, though abilities likely fill these), but the core workflows are well represented.

Maintenance

ActivityMaintained
ResponsivenessNo issues