WebinarStack

Create Webinar Draft

webinarstack.webinars.create_draft

Create a tenant-owned webinar draft from structured launch details.

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": {
      "title": "<title>",
      "thankYouUrl": "<thankYouUrl>"
    },
    "name": "webinarstack.webinars.create_draft"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes
`videoUrl`	No
`description`	No
`publicTitle`	No
`thankYouUrl`	Yes
`brandLogoUrl`	No
`thankYouMode`	No
`brandAccentColor`	No
`brandPrimaryColor`	No

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`errors`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the bar is lower. The description still adds real context by saying the record is a *draft* and *tenant-owned*, implying it is not immediately live and is scoped to a tenant. It omits duplicate-title behavior, validation failure modes, and what the draft's lifecycle state means.

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?

A single short sentence with the verb and resource front-loaded, so scanning is easy. The only waste is the vague "from structured launch details" clause, which occupies the position where a genuinely useful constraint could have gone.

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

Completeness2/5

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

Output schema exists, so return values need no explanation, but for a 9-parameter mutation tool with zero schema descriptions the definition is far too thin. An agent can infer the high-level action but lacks enough to fill the payload correctly or understand the draft's post-creation state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 9 parameters, so the description carries the full burden and does not meet it. "Structured launch details" gestures at the payload but explains none of the key semantics, notably the hosted/external thankYouMode enum, the empty-string-or-URI pattern on videoUrl/brand fields, or which fields are required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

A specific verb+resource pair ("Create ... webinar draft") plus a scoping qualifier ("tenant-owned") lets an agent separate this from siblings like create_test_registration or the many update_* tools. The trailing phrase "from structured launch details" adds no discriminating information, keeping it short of a 5.

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

Usage Guidelines2/5

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

The description never states when to use this tool versus alternatives, nor any preconditions (tenant context, permissions, whether a draft must later be published or can be edited via update_core_details). Nothing routes the agent between this and the sibling creation/update tools.

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?