WebinarIgnition

Read the questions of the live webinar

wi_get_webinar_questions

Read-onlyIdempotent

It reads the questions participants asked in the live console, the open ones and the answered ones, each with its id, the text, the name of the attendee, the time and the state. Take it when a host wants to know what people are asking or which questions are still waiting. "Are there questions I did not answer yet?" You give the webinar id and how many questions you want back. The ids come from this answer, so the next step can answer one or delete one without guessing. It changes nothing. Read-only, it changes nothing. Data comes only from the WordPress site this chat is connected to, the site the host approved, never from another site. Without a connected site the answer says what is missing and how to connect: no numbers and no example numbers. Words hosts use: live questions, open questions, attendee questions, Q and A

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": {
      "webinar_id": "<webinar_id>"
    },
    "name": "wi_get_webinar_questions"
  }
}

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.
`limit`	No	How many questions to return, 1-200. Default 50.
`session_id`	No	From an earlier turn (weiter · texte · stand).
`webinar_id`	Yes	The webinar (campaign) id, as wi_list_webinars returned it.

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

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered; the description adds real context beyond that: data is scoped to the connected WordPress site the host approved, and without a connected site the response explains what is missing rather than fabricating numbers. The repeated 'it changes nothing' is redundant with readOnlyHint but not contradictory.

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?

The core purpose is front-loaded, but the text is padded: 'It changes nothing. Read-only, it changes nothing.' repeats the same point twice, and the closing keyword list and 'no numbers and no example numbers' add bulk without much decision value.

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 an output schema present, return values need not be explained, yet the description still names the fields and explains the id-chaining workflow and site-scoping behavior. For a read-only list tool this is essentially complete, with only minor redundancy.

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?

Schema coverage is 100%, so the schema already documents webinar_id, limit, site, and session_id. The description only restates that you supply the webinar id and a count, adding no format or constraint detail beyond the schema, so the baseline 3 applies.

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 ('reads the questions participants asked in the live console, the open ones and the answered ones') and enumerates the returned fields (id, text, attendee name, time, state). This clearly separates it from siblings like wi_answer_webinar_question and wi_delete_webinar_question.

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 when-to-use trigger ('when a host wants to know what people are asking or which questions are still waiting') plus a sample user question. It does not explicitly name the alternative tools (answer/delete) as the next step, but it does say the returned ids enable answering or deleting without guessing.

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.