WebinarIgnition

Delete the webinar

wi_delete_webinar

Destructive

Deletes the webinar of this session from the connected WordPress site. Take it only when the host clearly wants it gone, for example "That test run has to disappear." It needs the session id, and the campaign when the session holds more than one. It cannot be undone: the campaign and everything attached to it are gone, so the host should say a clear yes first. It only deletes on the site of this sign-in; without an open connection it says how to connect and deletes nothing. Words hosts use: delete webinar, remove, test run, start over

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wi_delete_webinar"
  }
}

Input Schema

Name	Required	Description
`args`	No	the arguments for that ability, shaped by its input_schema.
`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.
`session_id`	No	From an earlier turn (weiter · texte · stand).

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"
+}

Changed1 schema field changedOct 20, 2026
- removedInput schema / required
```
Removed value: -[
-  "session_id"
-]
```
AddedOct 19, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Adds substantial behavior beyond the annotations (destructiveHint=true already signals danger): irreversibility, that the campaign and everything attached disappears, that it acts only on this sign-in's site, and that without a connection it reports how to connect and deletes nothing.

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-loaded with the action and the safety constraint, then requirements, then connection caveat, then vocabulary. Dense but mostly earning its place; the trailing 'words hosts use' list is useful for matching but makes the ending slightly list-like.

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 destructive, open-world mutation with an output schema and full schema coverage, the description covers confirmation, irreversibility, blast radius, and connection failure behavior — everything an agent needs before calling it.

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, but the description adds real meaning: session_id is mandatory and the nested campaign argument is required when the session holds more than one campaign — information the schema's 'args' and terse session_id description do not convey.

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?

Opens with a specific verb and resource ('Deletes the webinar of this session') and scopes it to 'the connected WordPress site', which cleanly separates it from siblings like wi_delete_webinar_logs, wi_delete_all_registrants, or wi_reset_webinar_funnel.

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 clear gating condition ('only when the host clearly wants it gone'), a concrete example, and a confirmation prerequisite ('the host should say a clear yes first'). The gap is that no sibling is named as an alternative, and listing 'start over' as a trigger word blurs the line with reset-style siblings.

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.